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?
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


convert a weakly named assembly to a strongly named

Hi,
I have one weakly named(i.e. not strong named) assembly/xyz.dll. And other
strong named assemblies/.dll. I have found that I cant use weakly named
assembly with strong named assembly.
How can I convert weekly named assembly to strong named assembly. Or other
possible way.
One more question: If I create assembly for C# with strong name. Can some
one else, who is not using strong name, will be able to use it in his C#
application without specifiying my strong name key.
Thank you.
Jul 21 05 #
Strongly named assembly wont load

Hi,
I have a C++ managed assembly (.dll) which links to a bunch of native
libraries. Everything works fine if I dont make the managed assembly a
strongly named one.
Once I make it a strongly named assembly by adding the following attribute:
[assembly:System::Reflection::AssemblyKeyFile("pub_ pri.snk")];
my test application (C# Test.exe) fails to load it and gives me the
following error:
An unhandled exception of type System.IO.FileLoadException occurred in
Test.exe
Additional information: Could not load file or assembly
Rimage.Rapid.Api.D, Version=2.0.6.1, Culture=neutral,
Strongly named assembly can reference only other Strongly named assembly

Hi,
Why strongly named assembly can refer other strongly named assembly ?
Thanks with Regards,
San.
Nov 16 05 #1 Post Reply Share this Question 1 Reply (adsbygoogle = window.adsbygoogle || []).push({}); P: n/a


HD Wallpapers
3D
3D Abstract
City
Celebrities
Indian Celebrities
Cars
Travel
Girls
Animals Birds
Movies
Sports
Black White
Nature
Planes
Anime
Food Drink
Dreamy Fantasy
Architecture
Games
Space
Holidays
Flowers
Love
Artistic
Baby
Beach
Bikes Motorcycles
Macro
Computers
Vector
Funny
Army
Textures
Brands
Misc
Music
Other
Privacy Policy - Copyrights Notice - Feedback - Report Violation - RSS 2017 © bighow.org All Rights Reserved .