Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / Internationalization / February 2005

Tip: Looking for answers? Try searching our database.

strong named assembly doesn't find satellite assemblies

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
RainerI - 22 Feb 2005 15:37 GMT
Hello everybody

i have an assembly which uses satellite assemblies. The ResourceManager
finds the resources and everything works fine. But when i make this assembly
strong named by placing [assembly: AssemblyKeyFile(<path-to-Keyfile>)] in
AsseblyInfo.cs and recompile my solution the ResourceManager doesn't find any
satellite assemblies. When i remove the strong name everything works fine
again.

What i have already tried:
- placing the assembly in the GAC
- making all satellite assemblies strong named
- placing the satellite assemblies in the GAC, too
- verified that the satellite assemblies have the save version number as my
assemblie

Nothing worked. Has anybody an idea what else i could try?
Thanks.
Marin Millar - 24 Feb 2005 19:28 GMT
Hi Rainer, Did you sign your satellite assemblies with the same
public-private key pair?  If the main assembly is signed, the satellite
assemblies must be signed with the same public-private key pair.  If you
have already tried that, then you may be able to find loading errors by
checking the log in fuslogvw.  Check Suzanne Cook's blog entry for more
information on how to debug loading failures.  
http://blogs.msdn.com/suzcook/archive/2003/05/29/57120.aspx
Your version numbers should also be the same, however, you can update your
main assembly without updating your satellite assembly by setting the
satellitecontractversionattribute - see more info here:  
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/
frlrfsystemresourcessatellitecontractversionattributeclasstopic.asp
Hope this helps,
Marin Millar [MSFT]
RainerI - 25 Feb 2005 13:05 GMT
Hi Marin. Signing the satellite assemblies and the main assembly with the
same private-public key pair and giving all assemblies the same version
number solved the problem.

Thanks a lot for your help.
Rainer Ilg

Rate this thread:







Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.