Upgrading from 7.1 to 8.0 for Openspan Automations ?
Is there a Best practice or step guide for converting from V7.1.* to V8.0.* in regards to Pega/Openspan Desktop Automations?
We have branched all source code in TFS, but when I open the main Solution, it starts to load all referenced Projects, but just stops/freezes on the second Project in the list, no error message....just sits there. Any ideas? When opening the Solution initially, VS2015 does display a popup screen in regards to a One-Way Upgrade. I clicked "Ok" and then it goes through each referenced Project and prompts for a Check-Out. Then it starts the "Loading Solution Projects..." and that is where it stops.
Accepted Solution
Updated: 19 May 2017 13:50 EDT
Unum
US
Ok..turned on Studio Logging, here is the last thing that is logged prior to it hanging:
Warning | 01:45:57.234 PM | 7 | MTA | Studio | | | 'UNUMPrj' Warning task: There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "ININ.IceLib, Version= Proprietary information hidden, Culture=neutral, PublicKeyToken=null", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
Given it is only a warning, not sure if this is truly the root cause of it hanging.....?
Pegasystems Inc.
US
Scott,
In your case it would be better to take the branched projects and open and convert them one at a time. Once all of the projects are converted - open them as part of your solutions. You may want to look at the paths in the solution file in a text editor to ensure that they are all pointed at your new branch.
Jeff
Unum
US
Thanks Jeff. (Hope all is going well with you!).
Yes, I have also tried that approach. I was able to pretty much get the VS Solution/Projects to upgrade as far as the One-Way conversion that Visual Studio does and I was also able to get Openspan to upgrade the Projects to version 8, except for the UnumPrj.osproj Project, it just hangs. I just have to kill the DevEnv.exe process in order to re-gain control of Visual Studio. At first I thought it was just taking a long time to convert that Project due to the size of it, but after letting it run for hours, I finally killed it. I have not been able to get past this one issue, so it is hindering our upgrade path. Any other thoughts..? Are there any Log files that I should be looking at...? If so, where would they be located...? I have looked at the Log4Net files in the Roaming/Openspan folder, but not finding anything that would point to the cause of this particular Project not loading or upgrading.
Regards,
Scott
Pegasystems Inc.
US
Make sure Studio logging is turned on. I would look in the StudioLog.txt to see what is happening. Send me an email and we can look at it on Monday if you are still stuck.
Accepted Solution
Updated: 19 May 2017 13:50 EDT
Unum
US
Ok..turned on Studio Logging, here is the last thing that is logged prior to it hanging:
Warning | 01:45:57.234 PM | 7 | MTA | Studio | | | 'UNUMPrj' Warning task: There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "ININ.IceLib, Version= Proprietary information hidden, Culture=neutral, PublicKeyToken=null", "x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
Given it is only a warning, not sure if this is truly the root cause of it hanging.....?