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.

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

[Beta Nice to Have] Migrations PowerShell: Support win81, wpa81, and portable projects #579

Closed
bricelam opened this issue Aug 21, 2014 · 0 comments
Assignees
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-enhancement
Milestone

Comments

@bricelam
Copy link
Contributor

Current thinking on this is that we will have a package structured as follows.

  • EntityFramework.Commands
    • lib/
      • portable-win81+wpa81/
        • .
    • build/
      • portable-win81+wpa81
        • EntityFramework.Commands.targets
    • tools/
      • EntityFramework.psm1
      • EntityFramework.Commands.dll

The . file allows the package to be installed into win81, wpa81, and portable projects. The targets file will copy the dll to the project's bin folder on build. The psm1 file contains the PowerShell commands which can then be invoked on the project using the copied dll. The commands will execute user code on Desktop .NET using the CoreCLR facades.

Note, this has been simplified to just the problem space; the commands package will also contain commands for net451, aspnet50 & aspnetcore50 projects.

@bricelam bricelam self-assigned this Aug 21, 2014
@rowanmiller rowanmiller added this to the 1.0.0-beta1 milestone Aug 22, 2014
@divega divega changed the title Migrations PowerShell: Support win81, wpa81, and portable projects [Beta Nice to Have] Migrations PowerShell: Support win81, wpa81, and portable projects Sep 3, 2014
@ajcvickers ajcvickers added the closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. label Oct 15, 2022
@ajcvickers ajcvickers modified the milestones: 1.0.0-beta1, 1.0.0 Oct 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

No branches or pull requests

3 participants