Closed niemyjski closed 7 years ago
Yes, please! I have been using this tool a lot and really want it on VS2017.
I agree we need this extension for VS2017. This is by far the most useful plugin I have ever used.
Upgrading to VS2017 should be relatively simple... but we also should upgrade it so that it also supports the new MSBuild Projects (ie .net core csproj)
I already have a working version for vs2017, i hope to release it soon... for supporting the new tooling, I need your help
I've added the VS2017 project, but somehow the projects cannot be loaded...
https://github.com/rsuter/NuGetReferenceSwitcher/commit/8682282072c08d525244421046e6860f73da54dd
Has anyone an idea?
You mean, visual studio has your extension loaded, but it doesn't show it? VS2017 has a reworked settings system. No more normal registry....
Yes, the menu entry shows up, the ui launches but it cannot load the projects of the loaded solution... And debugging is a pita because all is based on com obj.
Ok, with the latest VS 2017 update it seems to work.. here is the debug/test version... will do some more tests and release it via VS marketplace. This vsix is for everyone who cant wait (like me) :-)
REMOVED
Ok no, it is not really working...
It seems that it breaks when you have .NET Core (i.e. new MSBuild) projects in your solution. Just unload them first...
Because I need a verified account on VS marketplace, i cannot publish the extension yet. Here the latest release build:
@rsuter you should just be able to upload your extension in place of the existing one. I don't know why you'd need to be verified (I don't remember being verified for our extension). If you want to send out a tweet to dave kean / VS twitter account and put a link here I'll retweet.
As you can see, I have an extension for each VS version (2012, 2013, 2015) and I need to publish a new one for VS 2017...
You can reuse the vsix package (extension name) for multiple versions of visual studio. In the pkgdef you just put your supported versions.
Thanks -Blake Niemyjski
On Wed, Apr 5, 2017 at 12:42 PM, Rico Suter notifications@github.com wrote:
As you can see, I have an extension for each VS version (2012, 2013, 2015) and I need to publish a new one for VS 2017...
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/rsuter/NuGetReferenceSwitcher/issues/21#issuecomment-291939855, or mute the thread https://github.com/notifications/unsubscribe-auth/AA-So14EVn5ZdQLmUMAB74yESobNsWSKks5rs9KJgaJpZM4K64uH .
Good idea, do you have the time for a pr?
If I can get some time I will, I'm swamped pretty bad right now :(
It would be super nice if this could be updated for VS2017!