Friday, October 15, 2010

EP 64 bit machine deployment


(1)    If you are using  64 bit machine for EP, make sure getSharepointTemplatePath method of SysEPDeployment class in AOT has the below code . This is needed so that whenever you save user controls in VS, that will automatically be deployed to the EP server.

public static str getSharepointTemplatePath()
{
    xSession session = new xSession();
    int pointerSize = 0;
;
    pointerSize = System.IntPtr::get_Size();
    if (session.clientKind() != ClientType::Client && pointerSize != 4)
        return SysEPDeployment::getSharepointTemplatePathDotNet();

    return SysEPDeployment::getSharepointTemplatePathWin32();
}


If you are making change to user controls in Visual studio, then there are no additional steps to have these changes propagated to the EP Server. Whenever you make changes on already existing user control in VS, it will automatically copy it to the SharePoint folder location. If you are creating new user control, when you add it to AOT by the right click menu and save the control in VS, it will automatically copy it to the SharePoint location.
(3)    If you are making changes to Tables/EDTs/Enums/Data Sets/Classes, then you need to click the “Refresh AOD” link available to the administrators in the EP home site quick launch. This will clear the metadata cache. You can also do an “iisreset” if needed
(4)    If you are making change to proxy file/static files/resources, then you need to deploy them. User AxUpdatePortal utility http://msdn.microsoft.com/en-us/library/dd261467.aspx (Manage Deployment Option does not work in 64 bit machines,so you have to use AXUpdatePortal)

1 comment:

Patrick said...

Interesting. So you're testing .Net pointer size to see if the current machine invoking the method is 32 or 64 bits. That's a pointer size of 4 bytes or 8 bytes. Good idea!

EP development and administration is still a very heated topic it's great to see you contributing to the information available on the web.