Skip to content

Razor pages in a component should support @Namespace #9171

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
Closed
MarkStega opened this issue Apr 8, 2019 · 1 comment
Closed

Razor pages in a component should support @Namespace #9171

MarkStega opened this issue Apr 8, 2019 · 1 comment
Labels
area-mvc Includes: MVC, Actions and Controllers, Localization, CORS, most templates ✔️ Resolution: Duplicate Resolved as a duplicate of another issue

Comments

@MarkStega
Copy link

Is your feature request related to a problem? Please describe.

I don't want generated razor.g.cs files to create a namespace that is dependent upon the directory structure containing the .razor page.

Describe the solution you'd like

I believe that an @namespace directive in a rzor page should override the generated namespace. Currently adding "@namespace xyzzy" is ignored.

Describe alternatives you've considered

n/a

Additional context

VS2019/DNC 3.0.0 Preview 3
@Eilon Eilon added the area-mvc Includes: MVC, Actions and Controllers, Localization, CORS, most templates label Apr 8, 2019
@rynowak
Copy link
Member

rynowak commented Apr 8, 2019

This is already tracked here: #8007

@rynowak rynowak closed this as completed Apr 8, 2019
@rynowak rynowak added the ✔️ Resolution: Duplicate Resolved as a duplicate of another issue label Apr 8, 2019
@ghost ghost locked as resolved and limited conversation to collaborators Dec 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area-mvc Includes: MVC, Actions and Controllers, Localization, CORS, most templates ✔️ Resolution: Duplicate Resolved as a duplicate of another issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Eilon @MarkStega @rynowak