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

[Blazor - ASP.NET Core] Resolve Namespace conflits in the BuildRenderTree with the "global::" keyword #13220

Closed
MajdajkD opened this issue Aug 17, 2019 · 1 comment
Labels
area-blazor Includes: Blazor, Razor Components bug This issue describes a behavior which is not expected - a bug.
Milestone

Comments

@MajdajkD
Copy link

MajdajkD commented Aug 17, 2019

Hi guys!

Description:

I have an issue with the generated BuildRenderTree functions of my razor components.
The issue is the following: I have multiple namespaces containing the same segments (this naming convention is company policy (customer censored, this is a demo project, not a production one.)):
imports

I am using the default generated server-side template:
layoutmarkup

I get the following error:
error

Possible fix:

The namespaces in the generated component code should use the "global::" contextual keyword (like the old designer files did).
The following temporary fix solves the problem until the next cleaning (build works fine, rebuild re-generates the wrong code):
error

Edit:

The dotnet/razor#7670 enhancement could also provide a workaround.

@mkArtakMSFT
Copy link
Member

Hi. Thanks for contacting us.
We're closing this issue as there was not much community interest in this ask for quite a while now.

@ghost ghost locked as resolved and limited conversation to collaborators Mar 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazor Includes: Blazor, Razor Components bug This issue describes a behavior which is not expected - a bug.
Projects
None yet
Development

No branches or pull requests

3 participants