-
Notifications
You must be signed in to change notification settings - Fork 10k
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
View assembly location fails when path contains special characters #14501
Comments
@terrajobst who would be the right person to ask about a) Should we be using |
Spoke offline and in .NET Core |
I think @steveharter is the reflection owner these days. |
That is my understanding yes. @steveharter and @jkotas should double check what I told you :-) |
|
Shadow copying does not exist in ,NET Core. |
Correct, looking for files on disk like this is not going to work for proper single-exes that we are looking into for .NET 5, but that is a topic for a separate discussion. cc @rynowak |
I've filed a request to do that. |
@aL3891 do you have a small repro-app that I can use to test against? |
You can just make a new mvc webapp, build it, and rename the directory its in to For some reason i cant get the exact same issue but you do get an error and renaming the folder back to Calling the folder |
Come to think of it, the error that i do get:
is one we've seen for some time on asp.net core, probably back to asp.net core 2.0 on full framework and we could never figure out why, but it must have been that our build tools put a Of note is also that ´dotnet run´ doesnt work either with the above setup:
So this is probably a deeper issue than asp.net core itself |
Yeah, when I tried to do this locally I got
This would seem to imply that this is first and foremost a problem with the SDK, with an additional problem in MVC which may or may not continue to happen depending on how the SDK issue is fixed. Given that I'm going to move this issue over to the SDK repo. If we still run into this (or something like it) after their fix we can reassess. |
I wonder if its not even deeper than that actually, it seems to be an issue with post launch assembly loading or path handling in general |
Possibly. The end result here might be that we just don't support having escaped special characters in the path, but hopefully the SDK team at least knows more. |
This will be resolved by #14827 |
I'm not sure this is really a bug in asp.net or not but anyway,
As part of a service fabric deployment i have an app deployed in the following folder
C:\SFDevCluster\Data\_App\_Node_0\Fabric.AdminType_App121\Services.AdminPanelPkg.Code.5.29.0.3419f33.lu1b%2B%\
however when the app starts if failes to locate one of the view assemblies because its trying to use the following pathC:\SFDevCluster\Data\_App\_Node_0\Fabric.AdminType_App121\Services.AdminPanelPkg.Code.5.29.0.3419f33.lu1b+%
In other words, its unescaping the folder path so that
%2B
is turned into+
causing the lookup to fail.Additional context
The exception it self:
dotnet info:
The text was updated successfully, but these errors were encountered: