Can I force a program to load a weakly-named assembly when it's linked to a strongly-named assembly?



I have a program that references a strongly named assembly which is in the gac. I have a debug build of this assembly which I want to debug into, but it isn't strongly named. Can I use a policy file or something to force the program to use the weakly named assembly? Or do I have to recompile the program to reference the weakly named assembly? (These assembles are purchased from a 3rd-party. I have the source to them but I don't have the company's private key to strongly name my own build of them with the same key.)


Thanks,
Phil


Related to : Can I force a program to load a weakly-named assembly when it's linked to a strongly-named assembly?
Is it possible to apply a publisher policy to a strongly named, privately published assembly?
Programming Languages

I have created a common library at work, but unlike in this question, it is not published to the GAC. Instead, it is privately published to a company-specific installation folder.
EDIT: all the internal apps go into this same folder.


Is it still possible to apply a publisher policy, allowing older applications to use newer versions of the DLL? This article makes it sound like I can, but it's not totally clear to me.


If so, what should I distribute into my company-specific installation folder?


A config file for the common library? (policy.1.0.MyLibrary.config) (This would be easiest.)
A policy DLL for the com
Need a C# Assembly to reference a strongly named assembly loosely
Programming Languages

So here's the problem. I'm writing some StyleCop plug-in assemblies for use at the company I work for. As such, these assemblies need to reference Microsoft.StyleCop.CSharp.dll for example, which is strongly named.


The problem comes in that if I build this and pass it along to the developers in my group, they must have the same version of the StyleCop dll (currently 4.3.3.0) or it fails to load.


What is the best way to make my add-on rules DLL more independent? Should I just install my 4.3.3.0 version of those subordinate StyleCop dlls in the GAC? Can an assembly (vs an application) use a policy file?


Oh, and one of the main

Can I force a program to load a weakly-named assembly when it's linked to a strongly-named assembly?
Programming Languages

I have a program that references a strongly named assembly which is in the gac. I have a debug build of this assembly which I want to debug into, but it isn't strongly named. Can I use a policy file or something to force the program to use the weakly named assembly? Or do I have to recompile the program to reference the weakly named assembly? (These assembles are purchased from a 3rd-party. I have the source to them but I don't have the company's private key to strongly name my own build of them with the same key.)


Thanks,
Phil


c# - can you make a “weak” assembly reference to a strong named assembly
Programming Languages

For various reasons i would rather not use strong named (signed) assemblies in my project. however, one of the projects is referenced by a sharepoint web part which means it must be signed.


is it possible to have this assembly signed but when I reference it from other projects, to do so using a non-strong reference. this would give me the advantages of having a non-signed assembly for the rest of my code but still allow it to be loaded by sharepoint.


A strongly named assembly is required sporadic file not found when binding
Programming Languages

Our asp.net web servers are giving occasional binding problems which result in a page not being displayed to the end user. Pressing refresh usually works.


If you look in the event log you get the following entry:


Exception information:
Exception type: FileLoadException
Exception message: A strongly-named assembly is required. (Exception from HRESULT: 0x80131044)

Our assembly does have a strong name, however given that this works 99.9% of the time I don't see this as the problem. I have turned on fusion binding logging and when the error occurs we get a binding log file.



.net - Added a strong named assembly, but it is looking for unsigned assembly
Programming Languages
So, I have two projects... One is a big class library, and the other is a big simulator project.Originally during testing the assemblies were not strong-named, but now that I need COM visibility, I need to strong name them (I need this quick, and it is easier to make them COM visible rather than deal with the CLI).I generated a .snk and added it to the properties of each of the projects, the class library compiles just fine and outputs the .dll just fine. I added this .dll as a reference in

Privacy Policy - Copyrights Notice - Feedback - Report Violation - RSS 2017 © bighow.org All Rights Reserved .