-
Notifications
You must be signed in to change notification settings - Fork 264
Update VSIX to work with Dev17 #968
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.
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
Conversation
|
/azp run |
|
No pipelines are associated with this pull request. |
|
Could you consider taking a look to #918 to see if we can roll it in at the same time? |
kennykerr
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If @jlaanstra is happy with this that's good enough for me.
|
Dropping VS2017 support is somewhat unfortunate. VS2017 has one distinct feature that all successors are missing: The ability to deploy an application from layout to a USB-attached Windows 10 Mobile device, allowing immediate on-device debugging. Unless I'm the Last Man Standing that still supports Windows 10 Mobile for several applications, could you re-evaluate the cost/risk/effort of continuing VS2017 support, and ideally re-enable VS2017 that support? |
|
@tim-weis can you use an older version the VSIX for your VS 2017 install? Sadly as it is, we hardly have the resources to keep the VSIX running with the latest version. |
|
@kennykerr Where can I find older versions of VSIX for VS 2017? |
|
I don't actually know. I assumed the marketplace lets you download older versions, but there doesn't appear to be anything obvious there for finding older versions. Perhaps you can fiddle with the download link. |
|
thx! ex) |
This updates the VSIX to work with Dev17 (VS 2022) Preview.
One thing I learned is that the VCTargets install path was deprecated starting in VS2019, so I had to update it to an explicit path under MSBuild.
See:
The second link suggests that the new path won't work in VS2017, and I thought we didn't still support VS2017, so I've moved up the minimum VS version from 2017 to 2019.