Ef6: PowerTools: get it working on VS2015 and VS2017

Created on 14 Dec 2016  路  10Comments  路  Source: dotnet/ef6

PowerTools will need to be updated to work on VS2017. This will require access to the VS2017 SDK which should be available soon, and will require updating the vsix to V3 - again details on this should be available soon.

closed-wont-fix type-enhancement
Source
picture lajones
👍2

Most helpful comment

To summarize the current plan to ship PowerTools, we will:

  1. Remove the reverse engineering feature (@erikej has volunteered to send a PR)
  2. Do some smoke testing on the other features, in particular on VS 2015 U3 and VS 2017
  3. Publish the VSIX to the gallery
  4. In the release notes we note that customers can use the reverse engineering feature in the EF Tools or the Reverse POCO template for more flexibility.
picture divega on 8 Mar 2017
👍3

All 10 comments

@lajones Any particular reason why the PowerTools solution is currently targeting VS 2013? In other words - can I update to VS 2015?

ErikEJ picture ErikEJ on 15 Dec 2016

Also, my PR to get the VSIX fixed up for VS2015 was accepted but is not yet on VS Gallery. It's clearly needed as my blog post for doing it manually has now had almost 70K views ..still going at nearly 200 new views every day.

julielerman picture julielerman on 16 Dec 2016
👍2

@ErikEJ - no objection from me - I think it was just the last time this was touched.
@julielerman - @rowanmiller is usually responsible for releasing to VS Gallery - but he's on vacation. @diego - can you issue a release?

lajones picture lajones on 16 Dec 2016
👍1

See #154.

lajones picture lajones on 21 Jan 2017

To summarize the current plan to ship PowerTools, we will:

  1. Remove the reverse engineering feature (@erikej has volunteered to send a PR)
  2. Do some smoke testing on the other features, in particular on VS 2015 U3 and VS 2017
  3. Publish the VSIX to the gallery
  4. In the release notes we note that customers can use the reverse engineering feature in the EF Tools or the Reverse POCO template for more flexibility.
divega picture divega on 8 Mar 2017
👍3

@divega Good plan!

ErikEJ picture ErikEJ on 8 Mar 2017

Note from #264 and commit 4fe5c3c. Had to update the build to only work on VS2017. This is required so that the build will generate manifest.json and catalog.json within the resulting VSIX which are required for the VSIX to install on VS2017 and are ignored on VS2015 & VS2012 so it will install and run on those too.

lajones picture lajones on 9 May 2017

@lajones "Had to" - This is actually not required, unless you are unable/unwilling to build with msbuild14.

ErikEJ picture ErikEJ on 9 May 2017

@divega Close this? https://marketplace.visualstudio.com/items?itemName=ErikEJ.EntityFramework6PowerToolsCommunityEdition is published

ErikEJ picture ErikEJ on 27 Aug 2017
👍1

Close. We are going to recommend customers to use the Power Tools Community edition moving forward.

divega picture divega on 31 Aug 2017
Was this page helpful?
0 / 5 - 0 ratings

Related issues

FransBouma picture FransBouma  路  7Comments
AmirGeorge picture AmirGeorge  路  5Comments
ErikvdBurgwal picture ErikvdBurgwal  路  6Comments
leandrovip picture leandrovip  路  4Comments
divega picture divega  路  3Comments