Accessing the Location property of the "edge_nativeclr" assembly raises an mscorlib exception "Illegal characters in path"
See original GitHub issueWhen accessing the Location property of the “edge_nativeclr” assembly an mscorlib exception “Illegal characters in path” is raised.
Can be easy reproduced by creating a manual triggered Azure Function like this:
var list = AppDomain.CurrentDomain.GetAssemblies() .Where(a => a.FullName.StartsWith("edge_nativeclr")) .Select(a => a.Location).ToList();
Issue Analytics
- State:
- Created 7 years ago
- Comments:13 (7 by maintainers)
Top Results From Across the Web
Visual Studio build error "Illegal characters in path"
After hours of troubleshooting I tried to debug visual studio with another instance and get to the internals of the exception.
Read more >[Bug]: Illegal characters in path. #8762 - dotnet/msbuild
Issue Description. When I run MsBuild standalone from Visual studio, I get the following error: MSBUILD : error : This is an unhandled...
Read more >Illegal characters in path. - Microsoft Q&A
I am trying to create a new project through following procedure but visual studio is throwing exception.
Read more >Assignment 2 Performer system exception illegal ...
When there isn't a report to download, I am getting a log message that there are illegal characters in path (see screen shot...
Read more >Illegal Characters in Path
Hello Nicholas,. This behavior can happen if the Location column for the document in the workspace file table contains an illegal character. Can ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@CodeFromGround closing this as there will be no action at this point, but please let me know if you feel we need to reevaluate.
Fabio I would like to thank you for helping me with my issue. I truly understand that this is not a problem that resides in this repo, it’s further more a general problem. I will try to test a solution working with a separate AppDomain and check whether this is working for us or not. Beside that I would be happy if there is an option in the future to decide which assemblies are pre-loaded in the default app domain of an C# Azure Function. 😃