Get rid of the msi


I would much prefer it if the VS extension parts were deployed completely as a .vsix through the visual studio extension and updates tool. Then when you have another release, it would show up as an update in VS directly, no need to download and manually install another msi.

I'm guessing the reason why you use an msi is to get the binaries into the "Microsoft SDKs" folder which makes it easier for msbuild to find but I dont' think you should put it there at all frankly. Elevated permissions should never be required for this process, in my opinion. It would be much better if the only way to get the binaries was through nuget or download a zip off of codeplex manually. That's basically how it works with npm, you can do the same with nuget.
Closed Jul 28 at 10:18 PM by jonturner
As part of our move to GitHub, we're closing our CodePlex suggestions and asking that people move them to the GitHub issue tracker for further discussion. Some feature requests may already be active on GitHub, so please make sure to look for an existing issue before filing a new one.

You can find our GitHub issue tracker here:


danquirk wrote Feb 19, 2013 at 2:04 AM

Thanks for the report. You are right that we needed the MSI to do things VSIX installs alone are not allowed to do, but it does create this somewhat unfortunate dichotomy. I'm assigning to Jonathon who handles suggestions.