-
Notifications
You must be signed in to change notification settings - Fork 102
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
API Confilct #1681
Comments
This is expected right now. It will be resolved by the time this version is ingested in the .NET SDK as it requires some changes we are making there. For now, you can either use a fully qualified type name or a type alias to workaround it. |
Should we make an analyzer to point people to the correct class? |
I don't think it's worth it, given that:
So in practice once those two updates are in place, the only people hitting this will be expected to know what they're doing 🙂 |
Will this also resolve my issue with I get this error:
So far, I have not been able to resolve this one by fully qualifying the name. I am using it for this API: https://learn.microsoft.com/en-us/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.documents.textelement.textdecorations |
@Marv51 that's a known issue with some types, but it's only temporary because of a combination of things:
So for a temporary workaround, I'd recommend either upgrading WinAppSDK to preview, or downgrading the SDK to latest stable. Alternatively, if you're not using trimming in your project, you should also be able to work around this by temporarily setting |
Are you using |
Yes, I temporarily switched to Windows.ui.colors due to a conflict with the previous Microsoft.ui.colors api |
Describe the bug
API Confilct
To Reproduce
When I upgraded to CsWinRT CsWinRT 2.1.0-prerelease.240722.1, I compiled the WinUI 3 project and found that both Microsoft.UI.Colors and Windows.UI.Colors were referenced
Expected behavior
Keep one set of apis
Version Info
CsWinRT 2.1.0-prerelease.240722.1
Additional context
None
The text was updated successfully, but these errors were encountered: