Invalid format of DLL

G

Guest

I've compiled a number of projects that have a dependency on a DLL containing
the projects' dataset definitions. They're all VB.NET projects and compile
cleanly under one solution in Visual Studio.
I then move the resultant EXEs and DLLs to the company's server from my
local C: drive, and everything looks ok for about five minutes.
After about five minutes, when I try to execute the the EXEs, the message
"Invalid format for Dataset.dll" appears, and when I look at the properties
of the DLL, I find that the version tab has disappeared (it was there 5
minutes earlier).
Also, the EXEs' icons revert to the windows default.
It seems Windows XP is running some sort of background cleanup and disabling
the DLL and its dependent EXEs.
I'm not using strong names or the GAC.
Can someone tell me what the solution to this problem is? I suspect this is
some sort of .NET versioning control, but haven't a clue about fixing it. I
thought the CLR only took action with programs when its made to run them; not
whilst they're sitting in a library.

Thanks,
TrevJ
 
C

Chris Dunaway

The only thing that I know that WinXP does is their file protection
process. If a different version of a file (such as notepad.exe) is
copied into the Windows or System32 folder, Windows will silently
re-copy the correct version of it back in. You're not placing any
..dll's in any Windows System folder are you?

When you notice that your files have changed, do they still have the
same date/time stamp on the hard drive? Could you have a virus or
rootkit operating that affects .dll and .exe files?
 
K

Ken Halter

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top