-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
net5.0-windows fails because of WPF/XAML bug #14
Comments
This is due to a bug in WPF: dotnet/wpf#3404. Since this is not something we can fix in this project, I'm going to tentatively close it. Please do reopen if there is an actual fix at some point and we need to do something on this project. Thanks! |
This search shields a potential manual workaround alternative for your own repo: https://github.com/dotnet/arcade/search?q=_WpfTempProjectNuGetFilePathNoExt |
Thanks for the reply. |
Doesn't work within Blazor(server) apps as well. |
@springy76 could you link to the relevant MS issue on their side too, in case they are aware, so others can also track that as needed? |
Hi,
I tried ThisAssenbly for a console app, and it worked perfectly.
But didn't work for a windows app.
error CS0103: The name 'ThisAssembly' does not exist in the current context
csproj file is
Looks like ThisAssemly generates correct code and I can see the generated code, but windows app can't reference those code.
The text was updated successfully, but these errors were encountered: