Visual Studio and migrating to 2.19/2.20

[K.Wagrez]

Hello everyone,

I had a question relative to Unigine 2.20/2.19 and Visual Studio.

I saw here that, maybe in the specific context of a C# .Net integration, you were advising on moving to Visual Studio 2022:
https://developer.unigine.com/forum/topic/9110-unigine-219-major-optimizations-openxr-webrtc-video-streaming-usd-support-animation-improvements/

I was under the impression that, starting from 2.19, you upgraded to Visual Studio 2022 for compilation on your side (I don't remember where I saw that). However you still allow the creation of projects using Visual Studio 2015 in 2.19/2.20.

We are using/calling Unigine dlls through our own modules, which are compiled with Visual Studio 2017 currently. Can we expect trouble if we migrate Unigine to 2.19/2.20, without upgrading Visual Studio to 2022 to compile our own modules ?

We are not using the C# backend, we only do C++ (and some unigine scripts).

Thanks in advance !

[silent]

Hi Kevin,

Visual Studio 2022 is mostly mandatory if you are going to use C#.

You can still compile your C++ code using Visual Studio 2015 (or 2017) and link with engine library without any additional issues.

However, it's better to use latest compilers since they simply have better code generation (at least that's what we observe in our codebase) :)

Thanks!

[K.Wagrez]

Thanks for your quick answer silent,

We are very much enthusiasic about more recent IDEs and compilers, but, as you may know, change is also about money and authorizations :p. I wanted to make sure that we could still make our solution work with Unigine 2.20, while waiting for the greenlight for our VS upgrade !

Thanks again !