Upgrading from Release 9

  • 아티클

If your integration was created with Release 9 of Visual Studio Tools, use the following procedures to upgrade your integration to work with Visual Studio Tools for Microsoft Dynamics GP 2013. Separate procedures are included for C# and Visual Basic.

C# integration

Use the following procedure to upgrade a Visual Studio Tools integration created with C#.

  1. Open the solution for your integration.

    Using Visual Studio, open the solution file for the integration you want to upgrade.

  2. Use the Visual Studio Conversion Wizard.

    The Visual Studio project must be converted to work with the current version of Visual Studio. Complete the steps in the Visual Studio Conversion Wizard to convert the project.

  3. Rebuild application assemblies.

    If you had built any application assemblies for your integration, you will need to re-build them so they are up-to-date with the latest version of Microsoft Dynamics GP. Refer to Dictionary Assembly Generator for information about generating application assemblies.

  4. Set the version of the .NET framework to target.

    Visual Studio Tools for Microsoft Dynamics GP 2013 integrations must target .NET Framework 4 to build properly. To specify the target framework, display the project properties. In the Application group, set the Target framework field to .NET Framework 4. In the message displayed, click Yes indicate that you want to make the change.

    Warning: If you do not target the .NET Framework 4, you will see numerous build errors when you build your project.

  5. Update the assembly references.

    The assembly references for the project likely will be incorrect, because they won't refer to the new versions of the Visual Studio Tools components and application assemblies.

    Cc543551.VSTDGP_BrokenRefs(en-us,MSDN.10).gif

    Add references to the updated Visual Studio Tools assemblies, to replace the broken references.

    Warning: The reference to the Microsoft.Dexterity.Shell.UI assembly is a special situation. This component was merged into the Microsoft.Dexterity.Shell assembly. Create a reference to the Microsoft.Dexterity.Shell assembly, and delete the reference to the Microsoft.Dexterity.Shell.UI assembly.

  6. Update the namespaces used in integration code.

    The namespace for the shell (user interface) components of the Visual Studio Tools integration has changed. The namespace reference must be changed from:

    Microsoft.Dexterity.Shell.UI

To the updated value:

<pre class="checklistscript" IsFakePre="true" xmlns="http://www.w3.org/1999/xhtml">Microsoft.Dexterity.Shell

  1. Update the namespace references used for any forms.

    The same namespace change must be made for any forms you created for your integration. When you attempt to open a form in the Visual Studio designer, you will see an error similar to the following:

    Cc543551.VSTDGP_DesignerError(en-us,MSDN.10).gif

    This means that the code used for the form is using the old namespace, rather than the new Microsoft.Dexterity.Shell namespace. You must view the code for the form, and change all of the namespace references to remove the "UI" portion. This will be required in several places. An example of code to be fixed is shown highlighted in the following illustration.

    Cc543551.VSTDGP_FixingFormCode(en-us,MSDN.10).gif

    Hint: You may need to expand some hidden sections of the code to find all of the references.

    After making these changes to the form's code, save the updated file. Close the form designer if it is still open, and then re-open the form. The form should now open and have the updated Microsoft Dynamics GP appearance.

  2. Build the solution.

    Choose to build the updated solution in Visual Studio. You may encounter build errors if your integration references resources in Microsoft Dynamics GP that have been deleted, moved, or renamed. You will need to fix these issues and rebuild the integration.

Visual Basic integration

Use the following procedure to upgrade a Visual Studio Tools integration created with Visual Basic.

  1. Open the solution for your integration.

    Using Visual Studio, open the solution file for the integration you want to upgrade.

  2. Use the Visual Studio Conversion Wizard.

    The Visual Studio project must be converted to work with the current version of Visual Studio. Complete the steps in the Visual Studio Conversion Wizard to convert the project.

  3. Rebuild application assemblies.

    If you had built any application assemblies for your integration, you will need to re-build them so they are up-to-date with the latest version of Microsoft Dynamics GP. Refer to Dictionary Assembly Generator for information about generating application assemblies.

  4. Set the version of the .NET framework to target.

    Visual Studio Tools for Microsoft Dynamics GP 2013 integrations must target .NET Framework 4 to build properly. To specify the target framework, display the project properties. In the Compile group, click Advanced Compile Options. Set the Target framework (all configurations) field to .NET Framework 4, and then click OK. In the message displayed, click Yes to indicate that you want to make the change.

    Warning: If you do not target the .NET Framework 4, you will see numerous build errors when you build your project.

  5. Update the assembly references.

    The assembly references for the project will be incorrect, because they won't refer to the new versions of the Visual Studio Tools components and application assemblies.

    Cc543551.VSTDGP_BrokenRefsVBOnline(en-us,MSDN.10).gif

    Add references to the updated Visual Studio Tools assemblies, to replace the broken references.

    Warning: The reference to the Microsoft.Dexterity.Shell.UI assembly is a special situation. This component was merged into the Microsoft.Dexterity.Shell assembly. Create a reference to the Microsoft.Dexterity.Shell assembly, and delete the reference to the Microsoft.Dexterity.Shell.UI assembly.

  6. Update the namespaces used in integration code.

    The namespace for the shell (user interface) components of the Visual Studio Tools integration has changed. Any namespace reference must be changed from:

    Microsoft.Dexterity.Shell.UI

To the updated value:

<pre class="checklistscript" IsFakePre="true" xmlns="http://www.w3.org/1999/xhtml">Microsoft.Dexterity.Shell

  1. Update the namespace references used for any forms.

    The same namespace change must be made for any forms you created for your integration. When you attempt to open a form in the Visual Studio designer, you will see an error that prevents the form from being displayed. View the code for the form:

    Cc543551.VSTDGP_FixingFormCodeVB(en-us,MSDN.10).gif

  2. Update the form designer code.

    Open the "Designer" source file for the form to fix the references so they use the new Microsoft.Dexterity.Shell namespace. Change all of the namespace references to remove the "UI" portion. This will be required in several places. An example of code to be fixed is shown in the following illustration.

    Cc543551.VSTDGP_FixFormDesignerVB(en-us,MSDN.10).gif

    After making these changes to the form's code, save the updated file. Re-open the form. The form should appear in the form designer and have the updated Microsoft Dynamics GP appearance.

  3. Build the solution.

    Choose to build the updated solution in Visual Studio. You may encounter build errors if your integration references resources in Microsoft Dynamics GP that have been deleted, moved, or renamed. You will need to fix these issues and rebuild the integration.