-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Crash trying to get Windows.UI.Xaml.Application.Current
#158
Comments
@viniciusjarina thanks for taking the time to report this. Do you mind sharing the Visual Studio and UWP version information? |
|
@viniciusjarina Thanks for the version info. I'll see what I can do. I haven't touched this project or built UWP apps in years so the pace might be a bit slow 😄 |
Oh no worries. I end up tweaking the .cs generated. I just reported to let you (and potentially other users) know. |
@christianhelle @viniciusjarina This is the same problem I ran into and should be fixed by #157 . |
First of all. Thank you. Great project. This should built-in on VS. I dunno why Microsoft don't invest more in the UWP tooling.
I am using your extension but for some reason my application crash on Initialize calling
Windows.UI.Xaml.Application.Current
with Catastrophic failure. Don't ask me why.I removed the chunk
reswcodegen/src/VSPackage/CustomTool/CodeDomCodeGenerator.cs
Line 98 in ceb9f65
Would be nice to have some option that doens't try to call Windows.UI.Xaml.Application.Current
Thank you
The text was updated successfully, but these errors were encountered: