471,310 Members | 1,702 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,310 software developers and data experts.

Assembly load problem in Winlogon, Windows 2000 ..

Hello All..

We are attempting to load a .Net assembly DLL from
a GINA (Winlogon) DLL. This is a C# DLL, signed
and GAC'ed.

In Windows XP, this works fine. In Windows 2000
however, we get this exception:

System.IO.FileLoadException: The given assembly name or codebase, 'MyDLL', wa
s invalid.
File name: "MyDLL"
at System.Reflection.Assembly.nLoad(AssemblyName fileName, String
codeBase, B
oolean isStringized, Evidence assemblySecurity, Boolean throwOnFileNotFound,
embly locationHint, StackCrawlMark& stackMark)
at System.Reflection.Assembly.InternalLoad(AssemblyNa me assemblyRef,
stringized, Evidence assemblySecurity, StackCrawlMark& stackMark)
at System.Reflection.Assembly.InternalLoad(String assemblyString,
Evidence as
semblySecurity, StackCrawlMark& stackMark)
at System.AppDomain.Load(String assemblyString)

We have determined (I think) that this does _not_ mean
the DLL was not found.. there seems to be something
else about the assembly/DLL that bothers the loader.

Once the user is logged on to Win2K, this DLL works
fine.. it is the Winlogon invocation that fails.

Has anybody run into this sort of problem ?

Thank you..

Jul 22 '05 #1
0 1235

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

10 posts views Thread by jojobar | last post: by
13 posts views Thread by Thom Little | last post: by
4 posts views Thread by =?Utf-8?B?SmFu?= | last post: by
reply views Thread by rosydwin | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.