![]()
With Visual Studio 2017 (which is version 15) it should now be VS150COMNTOOLS. NET Framework is installed and the 120 Common Tools referenced is no longer valid. However, with Visual Studio 2017, a newer version of the. Because of this, it is able to find mt.exe in the next line. The first line calls “vsvars32” to set up the environment so paths to. Mt.exe -manifest "$(ProjectDir)MyAddIn.X.manifest" -outputresource:"$(TargetPath)" #2 The post-build step looks something like this: call "%VS120COMNTOOLS%vsvars32" NET utility (mt.exe) to embed a manifest file into the add-in’s DLL. The post-build steps defined in the add-in template call a. For a registry-free add-in to work, it needs to have information embedded in the DLL that Windows uses to load it without the information being in the registry. Actually, the compile step completes but the post-build step was failing. Once you have an add-in, the next step is to compile it. ![]() So watch for those templates to become available. This is something I’ll be doing soon in support of an Inventor Add-In class I’ll be teaching at Autodesk University this year.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |