Brian Kitt

PLEASE PLEASE PLEASE help with this. This is the absolute most annoying problem in the world. .NET will, at random, choose .DLL's in my projects to lock. I have no idea why it does this, and I have no idea how to get them unlocked. Sometimes it takes 3 or 4 reboots of the machine, then .NET will behave. This is so annoying and frustrating, that it makes .NET impossible to work with. I've had this happen with multiple projects and various different DLL's, and I've even formatted my hard drive and rebuilt my machine hoping to make this problem go away. Nothing works. I've attached the error message below. I am so desperate for a solution, that I will PayPal send $100 to anyone that can offer a solution that works. IISRESET DOES NOT HELP.

If I get this error, I will try to delete the DLL from my 'target' project. It is locked, so I cannot. If exit Visual Studio, then I can delete the DLL, but as soon as I compile again, I get the same error. Logging off doesn't help, rebooting doesn't necessarily help. Usually with enough reboots (sometimes 3 or 4) the problem will go away for hours, then come right back with a vengence. I have not noticed a pattern to this problem.

I've worked with .NET since 2000, and this is a relatively new problem. I suspect it is due to a recent 'security vulnerability fix' from Microsoft. I have rebuilt my machine 2 times trying to make this go away, but since the problem is so sporadic and random, I can't really tie the problem down to a specific piece of software that makes the problem start happening. However, I am current with Microsoft maintenance. Since I've worked with .NET for 6 years without problem, the only thing it can be is a recent Microsoft fix that caused this problem.

I currently have Visual Studio 6, .NET 2000, .NET 2003, and .NET 2005 all installed on my machine. The problem is not related to .NET 2005, because the problem happened before I installed .NET 2005, same is true with .NET Framework 2.

Server Error in '/CCOData' Application.


Re: Visual C# General Bug in .NET that randomly locks DLL's

Brian Kitt

By the way, yes, I have shut off Microsoft Index Server, and still get the same error.



Re: Visual C# General Bug in .NET that randomly locks DLL's

Akbar Khan

But Try to just restart the service.




Re: Visual C# General Bug in .NET that randomly locks DLL's

Brian Kitt

Which service

I've tried restarting the ASP.NET worker process.

I've tried restarting IIS.

I've configured, stoped, restarted, and reboot Indexing Server.

Nothing makes a difference.

I have all of the .NET framework directories specifically excluded in Indexing Server as per Microsoft recommendation, but I still get the random DLL locks.





Re: Visual C# General Bug in .NET that randomly locks DLL's

James Curran

VS.net will lock the assembly while debugging, and frequently "forget" to unlock it. If this happens, exit VS.net -- Do NOT delete the assembly. Reset IIS, then launch a browser an attempt to load the page. That should work. Restart VS.net and continue on with what you were doing.

Another possible cause for what you are seeing is that your ORMSupportClasses assembly wants v 1.x of some assembly while some other page wants v 1.y of the same assembly. Whichever loads first wins and the other page causes the crash. (Try running you application is it's own appliation pool in IIS)






Re: Visual C# General Bug in .NET that randomly locks DLL's

chicken008

You should search the right version of your SD.LLBLGen.Pro.ORMSupportClasses.NET11.dll
I suppose this error occur when you upgrade uour llblGenPro. That's also upgrade the dll, and consequently your project got the error. All you have to do is search your previous version dll and over right the new one in the Project directory/Bin.
Hope this work.