How to compile example mdl programs

Question

I have installed the latest Microstation Connect and SDK and am trying to compile some of the examples. Can anybody help me get this setup correctly?

Robert Hook · Answer

Hi Ken Adams , 
 I am sorry to see you having such a difficult time getting up and running with the MicroStation Developer Shell Requirements. I also wish I could directly point you to the SDK Readme Requirements typically located directly on docs.bentley.com, Through necessity I do know I updated the SDK requirements for Update 12 (due to be released any day) to ensure plenty of Microsoft Visual Studio requirements and installation resource references are available in the typical (local) MicroStation CONNECT SDK Readme. For MSCE SDK U12 and later I will certainly update the SDK Annoucements to reflect current SDK Requirements in full detail. 
 So, as you have found you will need to install/configure the "Microsoft Windows 10 SDK" option (even if you don't have Windows 10 yet) due to our product level make file assertion/requirements. I am looking into seeing if we can make that conditional (internal vs. external/public) since that component to the best of my knowledge if only for applications requiring Debug Diagnostics implementations (we do, but most app developers don't). 
 If the Windows SDK is installed and the developer shell can correctly locate your Microsoft Visual Studio "vcvars32.bat" file properly - you can check by typing: 
 set _SDKVSENV 
 Then the developer shell should be able to locate "mt.exe" using the Microsoft Windows "where.exe" to find the appropriate location, like: 
 C:\PROGRA~1\Bentley\MICROS~2>where mt
C:\Program Files (x86)\Windows Kits\10\bin\10.0.17763.0\x86\mt.exe
C:\Program Files (x86)\Windows Kits\10\bin\x86\mt.exe 
 The developer shell tries to correctly locate and initialize Microsoft's development environment (MSCE SDK U11/VS2015 and prior call vcvars32.bat, MSCE SDK U12/VS2017 and later call VsDevCmd.bat) to do all the proper and heavy lifting to configure it's toolsets properly and we rely on it for our build tools to work properly. 
 I believe in MSCE SDK U10 I provided a " build.bat " (has a -verbose option) that can make troubleshooting between developers easier so we can say "send me your 'build' output" and a user can type "build" or "build verbose" to get detailed build output and optional (verbose) full OS environment variables included. 
 So, if you are still having issues please try to " build verbose " your example and post your "Build-[YourAppNameHere]-Verbose-Output.txt", and I am sure we can straighten out any outstanding issue preventing you from compiling the SDK examples. 
 HTH, Bob