MicroStation SDK U13 issues.Visual Studio 2017 Professional

Hi Roald,

Roald Tvedt said:

What am i doing wrong?

I guess you do nothing wrong. I recommend to search this forum for similar discussions, because I think the issue and workaround were discussed here already.

If I remember right, the problem is that SDK relies on registry records created by some installers (not sure whether it's NET Framework, Visual Studio, MSBuild or something else issue). In recent versions, Microsoft decided to choose different approach, but it has not been reflected in SDK detection mechanism yet. So when you have older computer with a history of different NET 4.x frameworks and Visual Studio installations (because of NET SDKs, MSBuilds etc.), MicroStation SDK will probably work fine, because the records will exists from older installations. But when the installation is new and some older were skipped, the records are missing.

I am sure Robert Hook is able to provide more details.

With regards,

  Jan

Hi Roald Tvedt and Jan,

MicroStation CONNECT Edition Update 12 SDK had a few issues related to the Microsoft Visual Studio 2017 support added. Some of those changes (though not all 100%) to finally address VS2017 and future support (until next huge changes) will make it out in finally in the Update 14 release.  Since we are a couple months out from that release and future releases will now be spaced at 6-month intervals...

Given the above, two things:

1. If a user modifies any file that was installed by an MSI software install - future software updates (by design) ignore updating those user modified files.  My first recommendation would be to ensure a 100% clean install of the MicroStation SDK (please delete everything under the existing folder) then re-install the Update 13 SDK.  This has the possibility of ruling out this "MSI side-effect" and possibly resolving your build issues.
2. Since we are moving to approx. 6 month release cycles and since I want to ensure we can resolve and advance issue sooner to developers I have created a "staging area" that can be considered "SDK early access items" (to manually clean out before next release/update install) located here: SDK Previews where I have an existing area for MKI updates.  Please verify a clean install, then hopefully (today) I can put 2 or 3 early access preview mki files that should prove to be very robust and stable.  I ask if you do apply these to respond back (and mark) build issues resolved by the early access updates, and as you can imagine perform a clean install of the next public release when available.

I will update this response once the MKI files have been added and available for anyone to test/confirm build conditions against.

[20191017-RH: SDKPreviews MKI Files are available for use with MicroStation CONNECT SDKs (Update 12 and Update 13 only).Once Update 14 is available It will be necessary to perform a Full and Complete Clean Install of the next available Commercial Release SDK. Delete all prior files.]

Thank you and HTH,
Bob

Thanks a lot, Robert.

Just verifying that I have done a clean installation of mssdk10130048en.msi. Same issues.

Please notify when MKI files are available.

Roald Tvedt said:

Please notify when MKI files are available.

They are already I guess, see SDKPreview MKI File link in last Bob's answer.

Regards,

  Jan

Great. The new mki files really did the trick!

Thank you very much.

Robert Hook said:

Since we are a couple months out from that release and future releases will now be spaced at 6-month intervals...

Is this referring to the SDK moving to a 6-month release cycle or MicroStation CONNECT moving to a 6-month release schedule?

Hi Robert Huston,

Both the MicroStation product and SDK are in progress of moving towards a 6 month release cycle.

Bob

Hi Robert Huston,

Both the MicroStation product and SDK are in progress of moving towards a 6 month release cycle.

Bob

Good Afternoon Bob. I appreciate the response!