First, open up your Visual Studio. This post was most recently updated on August 24th, This applies to your local development environment. Problem Table of Contents.
How to change IIS Express to run in bit mode? Author Recent Posts. Antti K. Antti Koskela is a proud digital native nomadic millennial full stack developer is that enough funny buzzwords? That's definitely enough funny buzzwords! He's been a developer from starting with PHP and Java , and he's been working on.
I would also appreciate tips on how to debug problems like this in general. Could any of your referenced assemblies be using some stuff in old Unity library? I have a lot of projects in my solution and a lot of potential suspects It's not the assembly reference, you reference version 2. But at runtime, the CLR is finding 1. If you don't see that old DLL in your build directory then use Fuslogvw.
Look at your project's bin folder and see if your project's dll has a conflict in it's name. Just delete that one and then Rebuild your solution. That worked for me. If it can't load "one of its dependencies" the error should say which "one of its dependencies" can't be loaded. The current form is useless, it might as well say can't load thinggy — Paul McCarthy. Show 2 more comments. Active Oldest Votes. May be the output folder where all projects build their assemblies, has an old version of unity.
Slime recipe 2, 2 2 gold badges 29 29 silver badges 49 49 bronze badges. Nour Nour 4, 3 3 gold badges 36 36 silver badges 62 62 bronze badges. Where's the log file of FuseLogVw — Stiger. To avoid having to find the log file, you can specify a custom log path: Settings, check the Enable custom log path checkbox, enter a custom log path, refresh. Add a comment. Open IIS Manager Select Application Pools then select the pool you are using go to advanced settings at right side Change the flag of Enable bit application false to true.
NET Framework version" dropdown — Martin. You can also right click your project in VS. It worked. Well it was already True in my case , just for try. I made it False and it worked. When I merged a project from 1 server to another, this flag was indeed False again, thanks for the solution! Robotnik Robotnik 3, 2 2 gold badges 29 29 silver badges 46 46 bronze badges. If you don't believe this will work, at least try. I couldn't believe it myself until I did.
Moon - oof. BTW ultimate solution. Show 1 more comment. Try to clean Debug and Release folders in your solution. Then remove and add unity again. BlaM Aleksei Anufriev Aleksei Anufriev 3, 25 25 silver badges 31 31 bronze badges. This issue can be caused by a lot of things ScottRippey This worked for me to. I first deleted all. Stefano Lonati Stefano Lonati 6 6 silver badges 14 14 bronze badges. Dependency walker is great, but copying random DLLs from the internet to Windows is It's better to try to find the installer that provides those dlls.
DLL not found and led me to this stackoverflow question. Basically keep in mind could be looking at false positive for some files, link provides more detail. Jeremy Caney 5, 26 26 gold badges 39 39 silver badges 66 66 bronze badges. I believe there should be another issue, not related to Visual Studio edition. Actually it was developed by means of VS Community edition. Do you have any other extensions installed? Rebecca Rebecca Following worked for me.
Riddhi M. Check the Web. In most cases. NET manages to solve the DLL hell problem pretty well, but sometimes it all falls apart, and when it does in best case scenario we see something like this:.
It can be done manually with the use of regedit. Windows has a build-in tool called Fuslogvw. Any version will do since the tool is available from. NET version 1.
I personally prefer the other way:. This is my preferred way to diagnose. After dealing with many Microsoft loggs, I think the assembly binding ones are the best ones. The files are named using a pattern like this:.
If one of the projects in Your solution has a different version of the assembly this assembly may be copied with it down to the folder of the executable assembly often overwritten the version You would assume it should have.
This is the reason why it is a good practice to have all references pointing to a single version of a given assembly. The easiest way to make sure that this is the case is by using Package Manager from Visual Studio right click on the solution :.
0コメント