Reputation: 7237
Why .NET Core SCD application doesn't probe assemblies from the same folder?
I created a .NET Core application, and I configured it to copy all of the DLL files to the output directory:
<PropertyGroup>
<CopyLocalLockFileAssemblies>true</CopyLocalLockFileAssemblies>
</PropertyGroup>
Then for one server, I deployed the bin\Debug\netcoreapp2.0 folder to the server, installed .NET Core Windows hosting bundle and things worked just fine.
Yet on another server, I did the same thing and things didn't work and I encountered this assembly can't be found error.
I went ahead and confirmed that in dep.json file there are so many lines of dependencies that somehow guide the runtime to locate them from runtimes/win/lib/netstandard2.0 folder.
The question is, why doesn't .NET runtime search the existing for the assembly? And how to make it understand that the DLL it's searching for is right there besides the entry assembly and it shouldn't search for it in another location?
Upvotes: 0
Views: 125
Answers (0)
Related Questions
- Strange behavior when loading assemblies and its dependencies programatically
- Not all assemblies are being loaded into AppDomain from the bin folder
- My .net core published executable gives a different directory path than when running the code
- How to load assemblies located in a folder in .NET Core console app
- Load referenced assemblies from a .net core Integration Test project doesn't include referenced projects from tested API
- Net Core: Find Application Assembly Location from Integration Test
- How to redirect probing for assemblies in .NET Core?
- How to load a .NET Core assembly from an application written in .NET Framework?
- Where is the assembly file?
- How do I give my .net app secondary locations to look for dependent assemblies?