As it turns out Sql Server Debugging was checked On in my project; now who did that? The prompt for user credentials was for SQL server’s benefit because the ASPUser didn't have permissions. When the application crashed it didn’t release the debug session with SQL Server unless I stopped and started SQL server, or killed the aspnet_wp.exe worker process, or rebooted the machine which did both of the previous.

Turning off Sql Server Debugging resolved the issue; if not the problem.

Thanks again for your support!

I just got the same error message all of a sudden. I removed the local reference to this assembly, and just stuck it in the GAC. Its working fine now.

Ali

Slight modifications to the previous:

put the assembly in GAC, keep reference in the projects but set copy local to false.

Are you all developing on the same box as the webserver? This might be the problem then. In 2 years I've never had any problems with asp.net whatsoever but that's because I develop on box A and the website is on box B.

I am running IIS on my development machine and do so to make myself more portable (laptop).

I do find it strange that this error never cropped up until I upgradded to the 19-mar release of LLBLGen Pro. I used an older version for a full month in the same development environment.

Is there an actual corellation, I don't know, but there has been a lot of recent traffic on this topic.

The latest upgrade might have been a version upgrade as well for you (1.0.2003.1 to 1.0.2003.3). Which might have caused the problems for vs.net, I'm not sure.

There are a lot of people having this problem, when you search for the error in google groups. So it is something else than solely related to LLBLGen Pro runtime libs. Perhaps to signed assemblies (as the dreaded KB article says you shouldn't place signed assemblies in the bin folder... )

I had a problem very similar to this recently and it turned out to be the windows Indexing Service I disabled it and all was well.

Weird stuff You can exclude folders in the index service btw, so you can keep using it (although it's pretty useless in an asp.net world IMHO) and avoid the problem.