Click here to Skip to main content
15,886,026 members
Please Sign up or sign in to vote.
5.00/5 (1 vote)
This is not really a question as it is another response to so many having this issue on occasion. I just thought I would post what my resolution was to this issue.
----------------------------------------------------------------------------
I had been struggling with this issue and found many articles on how to fix. None of them helped me. So, I took a step back. In our shop, we work with branching. The issue I was having was that the same project in one branch worked (when MSDeploy was exceuted), another did not. When I compared the projects, I found this one entry (see below) was missing in the project file that was throwing the exception. When I would add it in the project (that was throwing the exception), MSDeploy worked, when I removed it, it failed again. Hope this helps as well

<project>
<propertygroup>
<vstoolspath condition="'$(VSToolsPath)' == ''">$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(VisualStudioVersion)

Posted
Updated 1-Jul-16 13:30pm

If this isn't a question, then it's in the wrong place! :laugh:

What I'd suggest is that you repackage this a little and write it up (with minimum code examples if possible) and post it as a tip: http://www.codeproject.com/script/Articles/Submit.aspx[^]
That way it goes into a searchable "knowledge base" of solutions which should mean it's easier for those that need it to find.

(The chances are that some people will close this as "not a question" which means it will disappear forever).
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900