SDK and Visual Studio 2022 upgradation

Hi Senthil,

Senthil Kumar said:

Request to specify whether SDK V10.15 is supported with Visual Studio Professional 2022

When it is defined that SDK requires Visual Studio 2017, you must use this version.

Of course the situation is not so strict, but using different versions means you use not supported tools / configuration.

You did not specify what API / language you use:

• For NET API (C# or other NET langauge), any tool, producing NET assembly of required version (NET Framework 4.6.2 now) can be used. So not Visual Studio only, but also Visual Studio Code or anythig else, with NET Framework SDK at background, can be used.
• For C++ API, the required C++ compiler (toolset) must be used. Because of changes in C++ ecosystem, implemented in recent VS versions, I think even VS2022 can be configured to use VS2017 toolset, but you must configure everything manully.

Of course you can use VS2022 as editor, but compiling can be done calling VS2017 compiler.

Senthil Kumar said:

or which version of
SDK needs to be used after upgradation?

The question is wrong, because SDK version is defined by MicroStation version, not vice versa. So when you use MicroStation CE Update 15, SDK CE Update 15 must be used.

The latest MicroStation CE Update 16.2 supports VS2019, and as discussed in this thread, VS2022 can be configured too, even when still not supported officially. But at least, bmake can be used to compile C++ code.

With regards,

  Jan

Hi Jan Šlegr,

Thanks for the clarification

I am using NET API 

Senthil Kumar said:

I am using NET API 

Follow Jan's suggestions.  Here's some more info about MicroStation .NET development.

Senthil Kumar said:

I am using NET API 

In such case your situation is, as I wrote earlier, simple: Because NET addins are standard NET Framework 4.6.2 assemlbies (when talking about current MicroStation CE U16.2), you can use any tool, producing NET Framework 4.6.2 dlls. To use Visual Studio 2022 (any edition) is the best solution in my opinion.

Regards,

  Jan

Jan Šlegr said:

To use Visual Studio 2022 (any edition) is the best solution in my opinion.

I would note that with VS 2022, there seems to be some additional steps when working with WPF and custom user controls that rely on the Bentley API. Controls that display properly in VS 2019 designer and prior will not render properly on VS 2022 unless you insert several lines of

if (DesignerProperties.GetIsInDesignMode(new DependencyObject()))
    return

anywhere that would be accessing the Bentley API on initialization.

Running your plugin will not cause any exceptions and will display fine at runtime. This is strictly a design time issue.

There is no meaningful exception information when you encounter this rendering issue, so finding where you need to insert this line can be tedious.   As such, I would not recommend moving a large project written with WPF over from VS 2019 to VS 2022.

Also note that if you are using MVVMLight, this has been deprecated in Microsofts attempt to migrate to Windows MVVM Community Toolkit (which is not available in .net 4.6.2)

Because of this, there will be exceptions in the VS 2022 designer that cannot be fixed without some annoying #ifdef solutions that are determined off of the current build mode..

Alternatively, you may also be able to find an alternative MVVM framework, but if you are working with an existing project that utilizes Mvvmlight, you will run into this problem :)