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

Implement new architecture of dotnet-ef and PowerShell commands for ASP.NET Core/.NET Core #5334

Closed
rowanmiller opened this issue May 11, 2016 · 3 comments
Closed

Implement new architecture of dotnet-ef and PowerShell commands for ASP.NET Core/.NET Core #5334

rowanmiller opened this issue May 11, 2016 · 3 comments
Assignees
@bricelam @natemcmaster
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-enhancement
Milestone
1.1.0

Comments

@rowanmiller
Copy link
Contributor

rowanmiller commented May 11, 2016 •
edited
Loading

Some things to consider:
@rowanmiller rowanmiller mentioned this issue May 11, 2016
Closed
@rowanmiller rowanmiller added this to the 1.0.0 milestone May 11, 2016
@rowanmiller
Copy link
Contributor Author

rowanmiller commented May 11, 2016 •
edited
Loading

Since GitHub doesn't support multiple assignees 😄... assigning to @bricelam to catch up with @natemcmaster and others when he is back in the office to discuss where have landed and where we go from here.

@rowanmiller rowanmiller mentioned this issue May 11, 2016
Closed
This was referenced May 25, 2016
Closed
Closed
@natemcmaster natemcmaster removed this from the 1.0.0 milestone May 25, 2016
@natemcmaster
Copy link
Contributor

Remarking for triage: this can wait until after RTM.

@rowanmiller rowanmiller added this to the 1.0.1 milestone May 26, 2016
@rowanmiller rowanmiller changed the title Sort out architecture of dotnet-ef and PowerShell commands for ASP.NET Core/.NET Core (xproj) Implement new architecture of dotnet-ef and PowerShell commands for ASP.NET Core/.NET Core (xproj) May 26, 2016
@rowanmiller rowanmiller changed the title Implement new architecture of dotnet-ef and PowerShell commands for ASP.NET Core/.NET Core (xproj) Implement new architecture of dotnet-ef and PowerShell commands for ASP.NET Core/.NET Core May 26, 2016
@bricelam bricelam mentioned this issue Jun 1, 2016
Closed
@natemcmaster natemcmaster mentioned this issue Jun 13, 2016
Closed
@natemcmaster natemcmaster mentioned this issue Jun 30, 2016
Closed
@bricelam bricelam mentioned this issue Jul 1, 2016
Closed
@natemcmaster natemcmaster mentioned this issue Jul 1, 2016
Merged
This was referenced Jul 8, 2016
Closed
Merged
This was referenced Jul 19, 2016
Merged
Closed
@natemcmaster natemcmaster mentioned this issue Jul 25, 2016
Closed
@natemcmaster natemcmaster mentioned this issue Aug 10, 2016
Merged
@natemcmaster
Copy link
Contributor

Additional things to consider:

@bricelam bricelam mentioned this issue Aug 11, 2016
Closed
5 tasks
natemcmaster pushed a commit that referenced this issue Aug 11, 2016
Split tools into VisualStudio and DotNet packages and implement ef.exe
9cc12d6 
Issues:

 - Fix #646 - implements assembly-based command line interface
 - Fix #5273 - Split tools packages into .Tools.DotNet and .Tools.VisualStudio
 - Fix #5334 - Refactor cmdlets/dotnet-ef to invoke ef.exe/ef.dll
 - Fix #5684 - Use nuspec's instead of Sake
 - Fix #5839 - throw warning when architecture is not in {x86, x64, AnyCPU}

Other changes:

 - Add --no-color and --no-appdomain to command line tools
 - Add --json option to 'dbcontext scaffold' and 'migrations remove'
 - Refactor the inside-man invocation for Tools.DotNet to use "ef.dll" instead of invoking .Design.exe.
 - Add native powershell module for processing/forwarding streams
 - Reorganize code
    *  💔 break up DotNet and VisualStudio command line tools into separate packages
    * Push down execution logic dode from Tools.VisualStudio into .Design.
    * Lift code from .Design.Core to .Design
    * Reorganize test projects
    * Create a powershell only project for Tools.VisualStudio
    * Move tests into appropriate test projects and adjust namespaces
@natemcmaster natemcmaster added the closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. label Aug 12, 2016
@natemcmaster natemcmaster mentioned this issue Aug 15, 2016
Closed
@bricelam bricelam mentioned this issue Sep 6, 2016
Closed
@ajcvickers ajcvickers modified the milestones: 1.1.0-preview1, 1.1.0 Oct 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bricelam bricelam

@natemcmaster natemcmaster

Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-enhancement
Projects
None yet
Milestone
1.1.0
Development

No branches or pull requests
4 participants
@bricelam @ajcvickers @natemcmaster @rowanmiller