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

Scaffolding: Can't use global namespace #24403

Closed
bricelam opened this issue Mar 15, 2021 · 0 comments · Fixed by #24388
Closed

Scaffolding: Can't use global namespace #24403

bricelam opened this issue Mar 15, 2021 · 0 comments · Fixed by #24388
Assignees
Labels
area-scaffolding closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-bug
Milestone

Comments

@bricelam
Copy link
Contributor

There is currently no way to scaffold a model into the global (aka empty, top-level, root, or default) namespace.

Step Unexpected result
<RootNamespace /> in project Namespace matches assembly name
dotnet ef ... --namespace "" Error: Unrecognized argument
dotnet ef ... --context-namespace "" Error: Unrecognized argument
Scaffold-DbContext ... -Namespace '' Ignored
Scaffold-DbContext ... -ContextNamespace '' Ignored
@bricelam bricelam added type-bug closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. area-scaffolding labels Mar 15, 2021
@bricelam bricelam self-assigned this Mar 15, 2021
bricelam added a commit to bricelam/efcore that referenced this issue Mar 15, 2021
@ghost ghost closed this as completed in #24388 Mar 15, 2021
ghost pushed a commit that referenced this issue Mar 15, 2021
@smitpatel smitpatel added this to the 6.0.0 milestone Mar 15, 2021
@ajcvickers ajcvickers modified the milestones: 6.0.0, 6.0.0-preview3 Mar 25, 2021
@ajcvickers ajcvickers modified the milestones: 6.0.0-preview3, 6.0.0 Nov 8, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-scaffolding closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants