Try OpenEdge Now
skip to main content
Online Help
Introducing the Progress Developer Studio for OpenEdge Visual Designer : Tasks : Working with .NET resources : Updating assembly references
 
Updating assembly references
When you install a new version of .NET controls, assembly references for projects that you developed under the previous version become out of date. If you want these projects to use the newer controls, you must update the references.
You use the Update Assembly References tool for this purpose.
You can launch the Update Assembly References tool from Progress Developer Studio for OpenEdge, but the tool actually runs outside the Eclipse framework. This topic provides basic instructions for using the tool; you can access more detailed online help when the tool is running.
When to update assembly references
You should complete the update procedure each time you install a new version of any control set. This recommendation applies whether you install a new release of OpenEdge that includes upgraded controls, a patch from Progress Software Corporation that includes upgraded controls, or a control set that you obtain from any other source. Failure to update assembly references may prevent existing OpenEdge GUI for .NET forms from running, and may also prevent the Visual Designer from opening existing forms or from functioning properly when you try to develop new forms.
Note: It is not necessary to update assemblies after applying a hot fix from Progress Software Corporation.
Automatic update of Progress assembly references
The first time you open a workspace that includes one or more projects with out-of-date assembly references, a dialog alerts you to the situation and asks whether you want to update the references. If you click Yes at this dialog, OpenEdge automatically updates all references to Progress assemblies, including those containing OpenEdge Ultra Controls (Infragistics controls).
If you decline this automatic update, you will not be prompted again to update the current workspace. You should manually run the Update Assembly References tool when you are ready to perform the update.
The automatic update procedure does not affect third-party (non-Progress) assemblies. Run the Update Assembly References tool when you install a new version of any third-party controls.
Files requiring updating
The Update Assembly References tool modifies references as needed in all instances of the files assemblies.xml and toolbox.xml. Potentially, there is one of each of these files in every project in a workspace, plus the toolbox.xml file for the global Toolbox.
Launching the Update Assembly References tool
You can launch the Update Assembly References tool either from an OpenEdge main menu or from a command prompt:
*From OpenEdge main menu, select OpenEdge > Migration > Update Assembly References.
*From a command prompt, open a Proenv command shell and enter updasmref.exe at the prompt. You can optionally include an argument specifying the assemblies.xml and toolbox.xml files to be updated as follows:
updasmref -files file_paths
Separate multiple file paths with commas.
Using the Update Assembly References tool
The procedure for updating the references depends on whether the controls are Progress controls (for example, OpenEdge Ultra Controls) or third-party controls. See the online help provided with the tool for instructions on each of these operations.
Updating assembly references to Progress controls
The tool automatically proposes the current version (that is, the assembly version installed with the current version of OpenEdge) for each reference to an out-of-date Progress assembly. Thus, with a single click you can update your references to Progress assemblies.
Updating assembly references to third-party controls
The tool lists all non-Progress assemblies and allows you to manually select or enter the versions that you want to use.
Restarting and recompiling
After updating assembly references, do the following:
*Restart Progress Developer Studio for OpenEdge if one or more projects in the current workspace use the updated assembly references.
*Recompile any projects that use the updated assembly references.