Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

My WPF project has a namespace error

See original GitHub issue

Error Tip: No type or namespace name “Windows” in namespace “test.wpf.system” (missing assembly reference?)

This error occurs when my project contains the System namespace. I predict this is due to the implicit namespaces of.net6. I tried <DisableImplicitNamespaceImports>true</DisableImplicitNamespaceImports> and <Using Remove="XXX.System" /> but it didn’t work.

Repeat steps： build project

Error Code： https://github.com/344089386/WpfTest

Issue Analytics

State:
Created a year ago
Comments:8 (4 by maintainers)

Top GitHub Comments

1reaction

miloushcommented, Oct 11, 2022

@chris-kruining correct, in this specific case - where the generated system types get “hijacked” - would be resolved if the generator used the global alias. In your case though, that would not help, because the window itself is already in a conflicting namespace.

0reactions

chris-kruiningcommented, Oct 11, 2022

I don’t think this has anything to do with implicit usings. You are introducing Test.Wpf.System namespace in UserInfo.cs and your window is in the Test.Wpf namespace. All System namespaces then resolve to Test.Wpf.System which has precedence.

So don’t do that. Technically you could argue that the code generator should use global namespace alias, though I think you would have to present a compelling justification for such change.

@miloush Wouldn’t this issue be resolved if the code generator applies the global:: prefix if a assembly is passed via the attribute? this related to my issue in #7173