After an arduous, month and a half long process of navigating through the sales prevention process at PSC I have managed to obtain 10.2B. And after only the second attempt I have even managed to get it installed and running!
The basic sanity checks all work -- I can start a session, start a database, open up OEA etc, etc...
However... when I point Architect at my 10.2A workspace and attempt to run it I am greeted with the following, rather unfriendly, message:
System.IO.FileNotFoundException: Could not load file or assemply 'Infragistics2.Win.v9.2, Version=9.2.20092.2017, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0b' or one of its dependencies. The system cannot find the file specified.
This means nothing to me.
When a compile the project I get lots of errors which seem to be closely related:
Assembly Infragistics2.Shared.v9.2
Location: Infragistics2.Shared.v9.2, Version=9.2.20092.2017, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb
Note:
This assembly is not available to the Class Browser.
The assembly could not be loaded from the global assembly cache or from the assembly directory of the project.
I'm sure that this means something but I have no idea what.
Any clues?
Check you assemblies.xml you will need to change it to point to the new version of Infragistics.
Openedge->Migration->Update assembly references
The key is that it happens when you run it!
All workspace upgrade routines don't upgrade your run/launch configurations. They will probably still point to 10.2A and that comes with a 8.1 version of the Infragistics Controls.
Open the "Run Configurations" Dialog under the "Play" button and check the OpenEdge version it's using.
chuimonster schrieb:
After an arduous, month and a half long process of navigating through the sales prevention process at PSC I have managed to obtain 10.2B.
Can you share details with us? I've got mine the day before X-Mas. (Maybe a separate thread?)
Maybe I'll share the details over a beer some time.
I'll remind you!
Bingo!
Julian gets the Gold Star!
That was true, it was using 10.2A but changing it made no difference.
At Exchange! .... oh wait ...
At Exchange! .... oh wait ...
More likely it's going to become a PUG meeting or so. Like the upcoming NEPUG meeting in April.