The type 'GlobalStaticResources' exists in both ...
#8750
Labels
area/code-generation
Categorizes an issue or PR as relevant to code generation
difficulty/medium 🤔
Categorizes an issue for which the difficulty level is reachable with a good understanding of WinUI
kind/bug
Something isn't working
Comments
jeromelaban
added
kind/bug
michael-hawker
added a commit
to CommunityToolkit/Labs-Windows
that referenced
this issue
May 11, 2022
michael-hawker
added a commit
to CommunityToolkit/Labs-Windows
that referenced
this issue
May 11, 2022
michael-hawker
added a commit
to CommunityToolkit/Labs-Windows
that referenced
this issue
May 12, 2022
michael-hawker
added a commit
to CommunityToolkit/Labs-Windows
that referenced
this issue
May 12, 2022
MartinZikmund
added
difficulty/medium 🤔
20 tasks
michael-hawker
added a commit
to CommunityToolkit/Tooling-Windows-Submodule
that referenced
this issue
Aug 30, 2023
Source code button navigates to component folder on GitHub (main branch) Most likely namespace is shown (hard-coded logic for now) - unoplatform/uno#8750 Shows and links to Uwp/WinUI packages on NuGet
michael-hawker
added a commit
to CommunityToolkit/Tooling-Windows-Submodule
that referenced
this issue
Aug 30, 2023
Source code button navigates to component folder on GitHub (main branch) Most likely namespace is shown (hard-coded logic for now) - unoplatform/uno#8750 Shows and links to Uwp/WinUI packages on NuGet
michael-hawker
added a commit
to CommunityToolkit/Tooling-Windows-Submodule
that referenced
this issue
Aug 30, 2023
Source code button navigates to component folder on GitHub (main branch) Most likely namespace is shown (hard-coded logic for now) - unoplatform/uno#8750 Shows and links to Uwp/WinUI packages on NuGet
|
@jeromelaban Can And I find it may hard to change to internal... |
|
How can I avoid this problem? Do not have the same root namespace for two assemblies project. Please make sure that no more than one RootNamespace in your csproj[s] is the same. |
|
We do not have a fix for this yet, the only way around this is to avoid having the same default namespace for assemblies. |
|
@jeromelaban For me, having the same default namespace is very common. And the error messages here are confusing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current behavior
When building an application, the following message may arise:
Expected behavior
The compilation succeeds.
How to reproduce it (as minimally and precisely as possible)
Craete an application which contains two projects that use the same default C# namespace.
Workaround
Change the default namespace to be different for each assemblies.
Works on UWP/WinUI
Yes
Environment
No response
NuGet package version(s)
4.2.6
Affected platforms
No response
IDE
No response
IDE version
No response
Relevant plugins
No response
Anything else we need to know?
This issue is caused by the fact that the code generator uses the default namespace to create the
GlobalStaticResourcesclass, and uses it in App.xaml generation to initialize resources. These types conflict because they can be found in two assemblies, with the same qualified name.The text was updated successfully, but these errors were encountered: