angelazhangmsft
angelazhangmsft
Hi @dong-dev, thanks for reporting this issue! We've investigated the issue with the .NET/MSBuild team, and a fix has been implemented. The fix will be available in an upcoming update...
@Marv51 - instead of using the Windows.* namepsace, you should migrate to the corresponding Windows App SDK namespaces. Here are docs on [Mapping of UWP APIs to Windows App SDK](https://docs.microsoft.com/windows/apps/windows-app-sdk/migrate-to-windows-app-sdk/api-mapping-table)...
Thanks @riverar for pointing that out! > How can I control the language used to get values for x:Uid for unpackaged Desktop apps? @HavenDV, we reopened https://github.com/microsoft/WindowsAppSDK/issues/1687 to track that...
@A-Ovchinnikov-mx, can you try setting the following property in your project as a workaround as documented in [Code analysis in .NET](https://docs.microsoft.com/dotnet/fundamentals/code-analysis/overview#treat-warnings-as-errors)? ```xml false ``` By default, the CA2257 rule should...
Need to check if fixed by #1105
Using latest internal build I still see the following warnings before building:
May be fixed if NETSDK1130 is resolved
Possible way to fix this is to have the interop project add metadata to the TargetPath item it returns with the name of the WinMD that the interop project is...
@Corillian - unfortunately we haven't been able to investigate this further yet. As a workaround, you can add a package reference to Microsoft.Windows.CsWinRT in your app to avoid the NETSDK1130...
@eerhardt this looks related to #999