Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add support for Visual Studio 2017 #93

Closed
csoltenborn opened this issue Jan 4, 2017 · 1 comment
Closed

Add support for Visual Studio 2017 #93

csoltenborn opened this issue Jan 4, 2017 · 1 comment
Assignees
@csoltenborn
Labels
enhancement
Milestone
0.9

Comments

@csoltenborn
Copy link
Owner

Many things have changed for us with VS 2017.

Migration instructions from MS

Release notes for VS 2017 RC
csoltenborn added a commit that referenced this issue Jan 4, 2017
@csoltenborn
first steps to supporting VS 2017 (#93), not working yet (at all :-) …
4f8d8aa 
…) - note that solution can only be opened with VS2017 by now
csoltenborn added a commit that referenced this issue Jan 10, 2017
@csoltenborn
added more appropriate package reference (#93)
e0e0b09
csoltenborn added a commit that referenced this issue Jan 10, 2017
@csoltenborn
activated release candidate on AppVeyor (#93)
c932c0a
csoltenborn added a commit that referenced this issue Jan 10, 2017
@csoltenborn
first steps to supporting VS 2017 (#93), not working yet (at all :-) …
c6f249e 
…) - note that solution can only be opened with VS2017 by now
csoltenborn added a commit that referenced this issue Jan 10, 2017
@csoltenborn
added more appropriate package reference (#93)
8044b4c
csoltenborn added a commit that referenced this issue Jan 10, 2017
@csoltenborn
activated release candidate on AppVeyor (#93)
50ee541
csoltenborn added a commit that referenced this issue Jan 16, 2017
@csoltenborn
fixed some tests (#93)
824897d
@csoltenborn
Copy link
Owner Author

csoltenborn commented Jan 22, 2017 •
edited
Loading

VSIX tests are completely broken since the API to install extensions appears to have changed (former running tests were by accident still running against VS 2015). Things tried so far:

  • updating all VS DLLs referred by the test projects to their pre-release 15.* versions (didn't help)
  • switching to Microsoft.VisualStudio.[Settings|Shell].15.0 DLLs. Compiler forces us to also change the references to Microsoft.VisualStudio.ExtensionManager* DLLs to the current versions, but then our code still doesn't work, since APIs have changed.

Disabled VSIX end-to-end tests for now, since we know that

  • integration with VsTest.Console.exe works in general (i.e., with option TestAdapterPath)
  • integration with VS 2017 works in general (due to manual tests)

Still, tests need to be fixed and re-enabled.

csoltenborn added a commit that referenced this issue Jan 22, 2017
@csoltenborn
disabled VSIX end-to-end tests for now (see #93)
1588973
@csoltenborn csoltenborn added this to the 0.9 milestone Feb 12, 2017
csoltenborn added a commit that referenced this issue Feb 14, 2017
@csoltenborn
fixed remaining projects, added PlatformToolSet for VS2017 (#93)
b431aab
@csoltenborn csoltenborn self-assigned this Feb 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@csoltenborn csoltenborn

Labels
enhancement
Projects
None yet
Milestone
0.9
Development

No branches or pull requests
1 participant
@csoltenborn