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

Get-Project conflicts with Entity Framework Migrations #5

Open
hartez opened this issue Feb 20, 2013 · 1 comment
Open

Get-Project conflicts with Entity Framework Migrations #5

hartez opened this issue Feb 20, 2013 · 1 comment

Comments

@hartez
Copy link
Owner

hartez commented Feb 20, 2013

With the module imported as it currently is, the Entity Framework Code First Migrations Add-Migration command fails because it uses a command named get-project which conflicts.

Need to come up with a non-conflicting name for this function, or a way to avoid the conflict if a function with the same name already exists.

@vatioz
Copy link

vatioz commented Feb 29, 2016

The standard way is to use module specific prefix before the Noun, aka command prefixes - https://blogs.msdn.microsoft.com/powershell/2009/09/20/whats-up-with-command-prefixes/

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

No branches or pull requests

2 participants