Visual Studio 2015 Post Build Events

[Anonymous]

I probably shouldn't be using it yet, but I am using Visual Studio 2015.

In VS2010, for a post build event on a Inventor add-in I had:

call "%VS100COMNTOOLS%vsvars32" mt.exe -manifest "$(ProjectDir)AppName.X.manifest" -outputresource:"$(TargetDir)$(TargetName).dll"; #2

Has anyone run this using VS2015? I don't think mt.exe is applicable anymore. Any ideas?

[nmunro]

If you copy and paste %VS100COMNTOOLS% into the folder location in File Explorer you will see that it points to C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\Tools. The VS100 refers to Visual Studio 10, so it is likely that VS2015 would be VS120. You should be able to find it pretty quickly.

Neil

[Vladimir.Ananyev]

For VS 2015 it should be 

%VS140COMNTOOLS%.

C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools

[Anonymous]

Neil, this does not compute.  Am I pasting a file, or a value?  Where do I find this file?

Here is the exact error I am getting, which hopefully is why it is not creating the dll file...

Severity Code Description Project File Line Suppression State
Error The command "call "%VS100COMNTOOLS%vsvars32"
mt.exe -manifest "Z:\VSProjects\InventorAddIn3\InventorAddIn3\InventorAddIn3.X.manifest" -outputresource:"C:\Users\sanderson\AppData\Roaming\Autodesk\ApplicationPlugins\StampDrawing\StampDrawing.exe";#2" exited with code 9009. InventorAddIn3

[mslosar · Accepted solution]

call "%VS100COMNTOOLS%vsvars32" mt.exe -manifest "$(ProjectDir)AppName.X.manifest" -outputresource:"$(TargetDir)$(TargetName).dll"; #2

This is a post build event...so after it's all complete is this just copying a manifest file? If so, is this very necessary? I'm migrating forward to a new machine and i've got VS 2017 only and it appears the syntax for this has changed more than just the VS100COMNTOLLS part of things. Is it really needed?