Skip to content

Upgraded to support VS2017#18

Merged
jaredpar merged 1 commit intojaredpar:masterfrom
justcla:master
May 1, 2017
Merged

Upgraded to support VS2017#18
jaredpar merged 1 commit intojaredpar:masterfrom
justcla:master

Conversation

@justcla
Copy link
Collaborator

@justcla justcla commented Mar 30, 2017

Can build and run in both VS2015 and VS2017

Can build and run in both VS2015 and VS2017
@@ -1,7 +1,9 @@
<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003" ToolsVersion="12.0">
<Import Project="..\packages\Microsoft.VisualStudio.Sdk.BuildTasks.14.0.14.0.12-pre\build\Microsoft.VisualStudio.Sdk.BuildTasks.14.0.props" Condition="'$(VisualStudioVersion)' == '14.0' And Exists('..\packages\Microsoft.VisualStudio.Sdk.BuildTasks.14.0.14.0.12-pre\build\Microsoft.VisualStudio.Sdk.BuildTasks.14.0.props')" />
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can just delete VS 14.0 support altogether at build time. I've been settling on the idea of limting activey F5 development to VS 2017.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could. But we don't need to. I very carefully implemented full VS2015/VS2017 round-tripping. This is the way we are encouraging all extension developers to build their VSIXes.

@justcla
Copy link
Collaborator Author

justcla commented Mar 30, 2017

Can we bring back VS2012/VS2013 run-time support?

@jaredpar
Copy link
Owner

jaredpar commented Apr 2, 2017

Can we bring back VS2012/VS2013 run-time support?

Sure. Should be as simple as:

  1. Changing the version of the WPF editor references to 12.0.0.0.
  2. Adding them as an installation target

I'm not sure why I ever changed 1 above.

@jaredpar jaredpar merged commit bcd2c3e into jaredpar:master May 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants