The automatic upgrade built into OpenSpan Studio will take care of most changes.  However there are a few that you need to do manually.

All of these steps are for solutions that use .Net code and OpenSpan adapters and projects.

1.   (This applies to all solutions with multiple projects using the OpenSpan 4.5 public release )

All the projects within a solution must use the same build directory.  In the code gallery samples, this is the build directory of the startup project, but it can be any directory.

To do this, right-click the project and select Properties.  Go to the Build tab and change the build directory.  You need to then click on a control outside of the build directory textbox for the change to be saved.

 2.  You will need to open one of the adapters in each project that has an OpenSpan adapter.  You need to make a simple change in it to force a refresh of the internal data structures.  I’ve used the CloseTimeout value for this by adding 1 to it, but any change will do.   If you use CloseTimeout, then you need to click on another property for the change to be saved.

 This second step is only needed for upgrading projects, if you create a new adapter then you do not need to take this step.

 3.   A reference to OpenSpan.Runtime.Core.dll needs to be added for upgraded solutions that start entire OpenSpan projects and not simply using adapters.  You can also remove the reference to OpenSpan.Runtime.dll from any C# or VB projects.

 4.  The syntax for calling a graphical automation has been improved since the Beta 2 version.

        In Beta 2 you called an automation as:   

                object o = os.ReturnThreeValuesAutomation.InvokeEntryPoint( "a", 1 );
       ArrayList arr = o as ArrayList;
       foreach ( object element in arr )
       {
          System.Diagnostics.Debug.WriteLine( element.ToString() );
       }

        In the public release you call it as:              

       ArrayList arr = os.ReturnThreeValuesAutomation.Execute( "a", 1 );
       foreach ( object element in arr )
       {
           System.Diagnostics.Debug.WriteLine( element.ToString() );
       }

where the word Execute is the name of your automation’s entry point.  The advantage to this is the automation’s name is now used and the parameters and the return value are strongly typed.