-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[Bug] Long project name (~20 char) throws System.ExecutionEngineException for UWP #12990
Comments
Your buid log doesn't contains errors (Rebuild all: 2 succeeded), so we can't investigate with that. There is one part of your build chain that doesn't deal well with long windows paths (more than 256char), but I can't tell which one, or if it's the XF tooling responsibility. in the meantime, a workaround is to use shorter project names, or move it up one directory |
Just to add even I noticed same issue highlighted by @CaseAlexander, but in my case project name is just Test. So not quite sure if it is related to long name. In my case, I Build and run the UWP application for Debug x86, application is launching fine, and then I clicked on some Button in my app to go to the Page (that page name is less than 20 char), and then below exception pop-up. But yes I have few other pages in my project which have names longer than 20 chars, not sure if that is the issue. If we try to Build and run the UWP application for Debug x86 2-3 times, then all of sudden it starts working fine. So it is intermittent. System.ExecutionEngineException |
I do believe you figured it out. The default install location for projects in VS (on my machine) is 'c:\Users\drjohn\source\repos', not a terribly deep path. So to test your idea, I created a folder 'd:\test' and created new Xamarin Forms projects in there named "Test" and "TestTestTestTestTest1". Just create new and run, no code edits or package updates. Everything was fine. Then I copied them both to the default location 'c:\Users\drjohn\source\repos' and the "TestTestTestTestTest1" project threw the exception. Copying them back to 'd:\test' and they worked fine. So it looks like using the default VS install location for new projects requires relatively short project names for UWP. Thank you! |
On a side note, I would say it is an issue with XF since I found that the issue is only present if using XF >= 4.8.0.1269. If I use XF 4.7.0.1351 no issues |
@CaseAlexander if you have a repro, or a log, we will investigate |
Sure, attached is a zip, just unzip to c: Using XF 4.8.0.1687
Using XF 4.7.0.1351 Just open the solution #2, run the program, and wait a few seconds. The exception will appear. |
I'm also seeing the same runtime System.ExecutionEngineException with my Xamarin.Forms project. UWP project name is 9 characters long. "An unhandled exception of type 'System.ExecutionEngineException' occurred in System.Private.CoreLib.dll" VS: 16.8.2 If I just keep trying to deploy it eventually works. |
@MattRames Seems not to be related to the project name length, but the path length of the entire solution. |
Might be a dup of #12884 |
@CaseAlexander My solution path length is 53 characters, the working path you posted above is 67 characters. |
@CaseAlexander (and others) can you test this on 16.8.3 ? I'm on 16.8.3 and I've tried running all the repos in here and they all run for me without any issues |
On 16.8.2 and 16.8.3 I get this error multiple times daily. Not sure it's related to the project name, but for reference. Here is my longest project name "AS.Mobile.DealerTools.UWP" with path "E:\Ag Spectrum\DealerTools\AS.Mobile.DealerTools\AS.Mobile.DealerTools.UWP" |
@bmacombe This #12884 (comment) fixed the issue for me.
|
@MattRames Thanks, I missed that one. I've added it and things seem better. I'll report back if I get the problem again. |
@PureWeen Tested on 16.8.3 and issue persists. Adding 'false' to csproj does fix it however, so that's good! |
My team started having the same issue this week.. |
I'm going to close this issue for now based on @ivanv-microsoft 's comment about 16.9 If this issue persist on 16.9 then we can revisit |
Description
If using a relatively long project name (20 char tested), UWP throws the System.ExecutionEngineException "Windows.UI.Xaml.Controls.RevealBackgroundBrush"
Steps to Reproduce
Expected Behavior
The project should launch with the Xamarin.Forms sample.
Actual Behavior
throws the System.ExecutionEngineException "Windows.UI.Xaml.Controls.RevealBackgroundBrush"
Basic Information
Environment
Build Logs
Screenshots
Reproduction Link
Workaround
build_log.txt
Working - Test.zip
Not Working - TestTestTestTestTest.zip
The text was updated successfully, but these errors were encountered: