locked
32bit Development but 64bit Deployment RRS feed

  • Question

  • We've developed a number of aspx components and Plug-Ins for CRM 4.0 in our development environment, and we've packaged these up for automatic deployment using a Visual Studio Deployment package.

    Things have been going well until we've come across a client that has a 64bit deployment of CRM.

    First off the installation scripts failed because the Launch Conditions were unable to locate the MSCRM web path within the Registry. I'm guessing that's because its a 64bit machine and it's looking in the wrong place, even though the keys are where I would expect them to be.

    I've not been able to sort this deployment issue out yet, but it did get me thinking. Given that we've developed our ISV site and Plug-Ins on a 32bit environment where do they go on a 64-bit machine? The Plug-Ins would normally be placed within Server\bin\assembly but this is sitting in the 64bit program files area, or does this not matter? And when we come to register the Plug-Ins will it be looking for the 32bit SDK's or try to use the 64bit versions that are already there.

    Does anybody have any advice or experience about developing for clients that have better kit than you! Do i need to make any changes because the deployment will be on a 64bit platform, and how do I get the Visual Studio Deployment Project to read the MSCRM reg keys on a 64bit machine?

    Many thanks

    Steve

    Tuesday, November 9, 2010 10:32 AM

Answers

  • Plugins go in the same place, irrespective of 32bit v. 64bit environments - i.e. the Server\bin\assembly subdirectory off the CRM installation directory.

    The manifest of any .Net assembly (e.g. a plugin) will reference dependent assemblies (like the SDK assemblies) by Strong Name, which includes the name and version of an asssembly, but not whether it is 32 or 64-bit, so it will load the assemblies that are there.

    I'm not sure about how VS Deployment Projects access the registry in this environment - that might be a question more for Visual Studio forums


    Microsoft CRM MVP - http://mscrmuk.blogspot.com  http://www.excitation.co.uk
    Tuesday, November 9, 2010 11:23 AM
    Moderator

All replies

  • Plugins go in the same place, irrespective of 32bit v. 64bit environments - i.e. the Server\bin\assembly subdirectory off the CRM installation directory.

    The manifest of any .Net assembly (e.g. a plugin) will reference dependent assemblies (like the SDK assemblies) by Strong Name, which includes the name and version of an asssembly, but not whether it is 32 or 64-bit, so it will load the assemblies that are there.

    I'm not sure about how VS Deployment Projects access the registry in this environment - that might be a question more for Visual Studio forums


    Microsoft CRM MVP - http://mscrmuk.blogspot.com  http://www.excitation.co.uk
    Tuesday, November 9, 2010 11:23 AM
    Moderator
  • Thanks David

    I will try Visual Studio forums for the Launch Conditions issue I'm having.

    Tuesday, November 9, 2010 11:59 AM