Gen EDGE

 View Only
  • 1.  Upgrading from Visual Studio 2015 to 2022 - requesting feedback

    Posted 15 days ago

    We will be upgrading later this year from VS2015 to VS2022 to support our Windows GUI clients.

    We will also be upgrading from Windows 10 to Windows 11 later this year (schedule as yet unknown).

    Just checking to see if there are any known issues with this type of upgrade that we need to plan for or be aware of.
    I have also opened a case on the support site.



    ------------------------------
    Doug Seaver
    Systems Development Services Specialist
    Gen Tool Support
    WisDOT
    Madison, WI, USA
    ------------------------------


  • 2.  RE: Upgrading from Visual Studio 2015 to 2022 - requesting feedback

    Posted 14 days ago

    Addendum. We are aware of the required PTF service level to support VS2022 and that is a prerequisite step for us.  Looking more for any issues between compilers (if anyone has encountered any).

    We have over 500 GUI clients and are considering the possibility of converting them to Vs2022 in smaller batches, meaning we would be running a "mixed" VS2015 and VS2022 environment until we can get them all converted. I don't believe the C++ runtime support will be an issue but am wondering if anyone has attempted this with any combinations of Visual Studio.



    ------------------------------
    Doug Seaver
    Systems Development Services Specialist
    Gen Tool Support
    WisDOT
    Madison, WI, USA
    ------------------------------



  • 3.  RE: Upgrading from Visual Studio 2015 to 2022 - requesting feedback

    Posted 13 days ago

    We're upgrading from VS2015 to VS2019.  The GUI executables don't run with the upgraded Gen runtimes from the PTF level you have to be at.  However, it's only the exe files that have an issue, not the dll files.  Since the exe files for Gen generated GUI clients are all the same code, we found that we could just generate one new client and copy it's exe file to replace all 1700+ exe files in our client folders and that worked.  Haven't found any issues so far in our testing.  The one issue I did find was that there is an additional new Gen GUI runtime file that had to be present in the client folders so make sure you get all the runtime files updated and include the one additional new file.  That took me a while to figure out that there was a new runtime file.




  • 4.  RE: Upgrading from Visual Studio 2015 to 2022 - requesting feedback

    Posted 13 days ago
    Thanks for the heads up about new runtime deployment. I’ve missed that before, too.
    I try to refer to this document for reference.

    Gen 8.6 GUI and COM Proxy Deployment (broadcom.com)


  • 5.  RE: Upgrading from Visual Studio 2015 to 2022 - requesting feedback

    Broadcom Employee
    Posted 10 days ago

    Yes the KB article 44954 Gen 8.6 GUI and COM Proxy Deployment should always have the latest/current Gen GUI application runtime file requirements.
    The .exe file issue Stacy referred to is related to the *862* PTFs (superseded by WKS86300) for dynamic MFC and the related exception that can occur is documented in KB article 227510 Gen application "unhandled win32 exception" OR does not open
    As Stacy said the .exe file is just a stub so the same file can be used by all deployed GUI cooperative clients (the client .dll files have the actual code specific to each client).



    ------------------------------
    Lynn Williams
    Senior Principal Support Engineer
    Broadcom Software
    Australia
    ------------------------------