Update to VSIX format v3 for VS 2017

Question

Update to VSIX format v3 for VS 2017

ChrisMaddock opened this issue 8 years ago · 11 comments

We should also use the bigger logo at the same time.

Answer 1 · 2016-11-25T14:21:08.000Z

For the icon, see comments about the sizes at nunit/nunit3-vs-adapter#268

Answer 2 · 2017-01-06T21:03:38.000Z

@OsirisTerje @rprouse - I've had a go at this, but it seems a little buggy, wondered if either of you could shed any light after doing the other extensions?

My extension project gets as far as building the VSIX, but then the build fails to launch the experimental instance with:

error VSSDK1081: Problem occurred while extracting the vsix to the experimental extensions path.

If I manually run the VSIX, it installs in a disabled state. I can then enable it and things seem to work ok - but at this point I'm not sure if it's a problem with the VSIX, or my VS15 install. 😕

Did either of you come across anything like this doing the other projects, or was it all fairly clean cut? I've pushed what I've done as issue-27 - if either of you would have a chance to try it out.

Answer 3 · 2017-01-06T21:50:28.000Z

(I should maybe add that I couldn't build any of the VSIXv3's we currently have, so the likelihood of my installation having a problem is maybe high...)

Answer 4 · 2017-01-06T22:00:12.000Z

I did have issues with my laptop, I could build the vsix, but not install it, the one I built worked for others though. On my workstation, everything seems to work fine. So, there might be some issues with VS too here, side-by-side, pre-beta releases or whatever. Try to see if you can make it work on a clean VM.

Answer 5 · 2017-01-06T22:03:08.000Z

I'll try your vsix tomorrow :-)

Answer 6 · 2017-01-06T23:20:46.000Z

Have you tried deleting your experimental instance? You will find it in C:\Users\{user]\AppData\Local\Microsoft\VisualStudio

Answer 7 · 2017-01-08T00:28:24.000Z

Thanks both. 😄

@rprouse - good idea, hadn't thought of that. No joy though, unfortunately.

Answer 8 · 2017-03-18T12:02:23.000Z

@ChrisMaddock Did you work out what's causing the error VSSDK1081: Problem occurred while extracting the vsix to the experimental extensions path. issue? I'm getting the same thing with one of my VSIX's. Here is a potential fix: dotnet/fsharp#1751

Answer 9 · 2017-03-18T13:57:17.000Z

@RehanSaeed - I planned to try again in a later RC and see if they fixed it, but afraid I never got back to it. The fix you posted looks promising though, thanks for that!

I don't have a VS2017 installation right now, ill have to redownload and try again.

Answer 10 · 2017-04-01T16:04:38.000Z

@RehanSaeed - turns out my issue was https://github.com/Microsoft/extendvs/issues/41 - which I found via your post at ligershark/template-builder#96 (comment).

Thanks for sharing the outcome of your struggles - now finally got it up and running!

Answer 11 · 2017-04-01T17:28:00.000Z

Glad you got it sorted. Was a nasty bug!