Problem with SDK and compile - "MSBuildToolsPath is not specified for the ToolsVersion "14.0"

Hello

Have error "MSBuildToolsPath is not specified for the ToolsVersion "14.0"" the error message which has a reference to ""HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\14.0""
When I run Regedit I do not see the 14.0 entry.
When I run C:\Windows\SysWOW64\regedt32.exe I see the 14.0 entity.

When I just run regedt I do not see the 14 entry.

I will look into updating the installs
Thanks
Peter

  • Hi Peter,

    since Jan is on vacation, I will quote him:

    "unfortunatley because your provided not many information, it's hard to guess what can be wrong.

    Please read and follow this forum best practices, namely specify exactly what MicroStation and MicroStation version do you use, and also using what Windows.

    No until you provide more information:

    • What NET Frameworks are installed on your computer? ... there can be more and as was discovered, when original 4.6 is missing and only 4.6.2 is installed, using (only) the latest SDK an error is reported.
    • What Visual Studio is installed.
    • What SDK example did you try.

    You should also create and analyze verbose output (build example using verbose option) and also attach it to this discussion as crucial source of information.

    With regards,

      Jan"

    Mit freundlichen Grüßen / Best regards
    Volker Hüfner

    |  AB_DATE Engineering  Software   |  ab-date.de  |

  • Hello Volker,

    I have the Visual Studio Community 2019 edition installed. I did uninstall all the version of Visual Studio and reinstalled Visual Studio Community 2019 edition. This did not address the error being displayed.

    In review of the make (.mke) file I changed one of the settings from "BUILD_USING_VCE2008" to "BUILD_USING_VS2005". This having a value of 1.

    This change seemed to address the specific error. I still am working on other items

    Regards,

    Peter

  • Hi Peter, 

    I guess you are using some MicroStation V8i? In this case you will need Visual Studio 2008/5. I work now for quite some time with Bentley SDK and it always gives trouble if you do not use the proper Visual Studio. 

    In our V8 development, we use Visual Studio 2017 as Editor, but the makefiles uses Visual Studio 2008 for compilation.  Every try to substitute the VS2008 with VS2010 or later was a flop, and not worth the work.

    Even with CE I would recomment VS2017 since UP12 and VS2015 earlier.

    The mki-system in the SDK is on the one hand genius, but on the other hand very narrow minded. So the best way ist not to mess up with the SDK :-)

    Mit freundlichen Grüßen / Best regards
    Volker Hüfner

    |  AB_DATE Engineering  Software   |  ab-date.de  |

  • Hi Peter,

    The MicroStation V8 SDK sets the requirement of Visual Studio 2005 Professional.

    If other (editions or) versions are used you may be required to make additional changes to get those environments wired in to work properly.  We don;t advise this, but subtle changes to any BUILD_USING_VSxxxx might be relatively safe.  Please observe and exercise standard (Microsoft) cautions when passing pointers and types between different Visual C runtime libraries outside the required version that will likely lead to runtime exceptions/crashes.

    Bob



  • Hello Bob, Volker,

    I agree the proper version is required. I though I had the issue addressed but it is still there

    When the MDL.MKI file gets included it causes the error.

    Thanks for your time

    Peter

  • When the MDL.MKI file gets included it causes the error

    mdl.mki has been a reliable component of the MicroStation build tools for decades.  Without that set of rules in place you won't get far.  mdl.mki does not cause an error.  Something else is causing the error.

    Please confirm...

    • The version (e.g. v8.x.y.z) of MicroStation that you are using
    • The version(s) of Viz Studio that you have installed
    • The version(s) of .NET runtime that you have installed

     
    Regards, Jon Summers
    LA Solutions

  • Hello Jon,

    I updated the registry, I removed the entry for 14.0 and the issue seems to be addressed. Still checking things

    Microstation 08.11.07.171

    Visual Studio Community 2019  16.0.1

    Microsoft .NET Core SDK 2.1.602(x64) 2.1..602

    Microsoft Windows SDK for Visual Studio 2008 SP1 Express tools for .NET Framework  3.5.30729

    Thanks,

    Peter

  • Microstation 08.11.07.171
    Microsoft Windows SDK for Visual Studio 2008
    Visual Studio Community 2019

    So you don't have installed a version of Viz Studio compatible with MicroStation V8i (Viz Studio 2005)?

     
    Regards, Jon Summers
    LA Solutions

  • Hi Peter,

    As you are making more progress, I would like to suggest a couple items I use/used to identify specific needs/dependencies when building the first MicroStation CONNECT SDK (minimal environment and legacy arg support).

    1. It is best (as a quick sanity check of the environment) to try to get the myapp example compiling first.
    2. Though a bit verbose, I recommend using bmake using "+avilC" to provide the most robust/full logging option available to help troubleshoot build dependency issues/errors.
    3. When problem solving outside the build system to identify Registry, File, and/or Permission dependencies/issues, I prefer to use Microsoft Process Monitor (procmon) to provide those tough to find details that may not often bubble up to a user level, or get reported by applications providing useful messaging.

    Glad to hear you making progress.

    HTH,
    Bob



  • Hi Peter, 

    As everyone tries to tell you:

    Bob: The MicroStation V8 SDK sets the requirement of Visual Studio 2005 Professional

    Mit freundlichen Grüßen / Best regards
    Volker Hüfner

    |  AB_DATE Engineering  Software   |  ab-date.de  |