assembly-resolution

After installing Slow Cheeath (v. 2.5.10.3) to two projects in my solution, I am receiving the following error: "The "SlowCheetah.Xdt.TransformXml" task could not be loaded from the assembly C:\Users \User\AppData\Local\Microsoft\MSBuild\SlowCheetah\v2.5.10.2\SlowCheetah.Xdt.dll. Could not load file or assembly 'file:///C:\Users\User\AppData\Local\Microsoft\MSBuild \SlowCheetah\v2.5.10.2\SlowCheetah.Xdt.dll' or one of its dependencies. The system cannot find the file specified. Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and

Problem After installing the Microsoft ASP.NET Web API OData package 5.0.0-rc1 prerelease I end up with the following exception: Could not load file or assembly 'System.Web.Http, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) My MVC 4 project is brand new and really small, nothing fancy in it. I target .NET framework 4.5 I need this nuget package to implement PATCH using the Delta class (When I use the version 4.0.0.0 of the

Out of curiosity, I've created 2 assemblies which both have a class ( Class1 ) with the exact same namespace ( Library1 ). I then create another client referencing those 2 assemblies and try to create an instance of Class1 . The compiler, not surprisingly, gives me a compile-error about the ambiguous reference. Is there any way to explicitly specify the type in the assembly I want to use to avoid the ambiguity? Note: I know this rarely, if ever at all, happens in practice. It's just a question out of curiosity about language feature. CMS I think you should use an extern alias to wrap the

How are assemblies resolved in .NET. I mean, how is an assembly with a fully qualified name resolved. I am confused about the public/private key tokens and strong naming. Thanks EDIT: I have also read about delayed signing and stuff like that. Do people really use it? (Has anyone actually used delay signing) Who generates the key to sign an assembly. I am sorry if I am asking too many questions. But, I am confused about this whole thing. Strong naming is used together with a "public key token" to produce an assembly full display name ( mscorlib, version=2.0.0.0, Culture=neutral, PublicKeyToken

We are using version 4.1 of the validation application block. I am relatively new to it so I was wondering if it had the ability to either abstract out the configured namespaces and assemblies or otherwise provide proper validation of their existence? We had an issue recently where someone moved a class and didn't update the validation configuration file with the new namespace. As a result the validations were no longer being applied to the object. The application block seems to just ignore the discrepancies. Unfortunately this was not caught during the normal QA cycle. Is there any built in

I have a custom .NET assembly with some powershell cmdlets than I use for common domain related tasks. I've just created a new cmdlet that references a 3rd party library that has a reference to Newtonsoft.Json 4.5.0.0. However one of my other projects uses the latest version of json.net (6.0.0.0). So at runtime in powershell fusion throws an error saying it can't load newtonsoft.json 4.5.0.0. I've tried creating a powershell.exe.config and putting an assembly redirect in there: <?xml version="1.0" encoding="utf-8"?> <configuration> <runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com

I've a working XML Web service written in ASP.Net. Now I need to reference certain assemblies lying in a specific folder e.g. c:\NotMyCode I do not want to copy/duplicate zillions of dlls in that folder into my bin folder. I tried to keep the CopyLocal=false for the assemblies referred in the Web Service. That ended up in a FileNotFound exception for the assembly. When I switch to CopyLocal=true , the referenced DLLs are copied over to the bin folder.. and it works. So my question here is: How do I reference assemblies that do not lie in my bin folder or a subfolder beneath it ? Do I need to

I think this is likely to be a generic .NET assembly loading question, but in my specific case, I want my SharePoint Features to point to an assembly whose versioning is associated with the correct SVN revision number. My assemblies are now versioned as mentioned in this article . I'd like to be able to just configure my SharePoint features to use the latest version of the assembly that's in the GAC. <Feature Id="7b5d86e8-17dc-4943-8f4e-ad1068daf4f9" Title="My happy feature" Scope="Web" Version="1.0.0.0" Hidden="FALSE" DefaultResourceFile="core" ReceiverAssembly="HappyFeature, Version=1.0.0.0,

using the code How to embed a satellite assembly into the EXE file provided by csharptest.net, I've created a custom assembly resolver and embedded my assemblies in my resources. I can successfully resolve my assemblies used in but somehow AppDomain.CurrentDomain.AssemblyResolve asks for an assembly called 'AppName.resources' specifically "MyProgram.resources, Version=0.15.3992.31638, Culture=en-US, PublicKeyToken=null" which i don't know how to resolve? I've tried to disable loading my custom assemblies from resources (placed all my assembly dll's in program directory) and just enabled