Runtime is the version of the CLR (or .NET framework) the DLL needs (usually as a minimum), version is the DLL’s version. So long as you have the minimum runtime installed, it should be usable. However as a general rule it is usually best to select the latest version of the library for the latest … Read more
If you mean programmatically, use Assembly.GetReferencedAssemblies. You can use that recursively to find all the assemblies you need. (So you find the dependencies of X, then the dependencies of the dependencies, etc.)
UPDATE May 2019 : It works perfectly with Visual Studio 2019. UPDATE May 2022 : as mentioned by @Igor Meszaros It also works with Visual Studio 2022. To anyone that is using Visual Studio 2017, there is the latest method : From our beloved IDE, go to “Tools > External Tools…” and “Add” a new … Read more
I had the same problem. I used Microsoft Asp Net WebApi Client 4.0.20710 and it worked for me. Type the following command into Tools > Library Package Manager > Package Manager Console: Install-Package Microsoft.AspNet.WebApi.Client -Version 4.0.20710
Which reference-type you get depends on how you link the assembly. select the referenced assembly in the project-explorer go to the properties-page there you find a boolean flag “specific Version” true means: the assembly must have version=xxx false means: ignore the assembly version (I only have a german-vs2010 so the english translation for the german … Read more
It is possible to link to a shared assembly info file in VS 2010. Ashish Jain has a good blog post about it: Sharing assembly version across projects in a solution. After creating the shared assembly info file at the solution level, his instructions for linking to it from a project are: Right click on … Read more
I just needed to click “Unblock” in the file properties dialog in Windows Explorer.
For my scenario, I found that there was a identity node in the web.config file. <identity impersonate=”true” userName=”blah” password=”blah”> When I removed the userName and password parameters from node, it started working. Another option might be that you need to make sure that the specified userName has access to work with those “Temporary ASP.NET Files” … Read more
Add this code in web.config under the <configuration> tag as shown in image below. Your error should then be gone. <configuration> <appSettings> <add key=”owin:AutomaticAppStartup” value=”false” /> </appSettings> … </configuration>
One fairly nasty way would be: Type[] types; try { types = asm.GetTypes(); } catch (ReflectionTypeLoadException e) { types = e.Types; } foreach (var t in types.Where(t => t != null)) { … } It’s definitely annoying to have to do this though. You could use an extension method to make it nicer in the … Read more