I don't know what I did but when I compile my web app and go run it in a web browser I get the following error:

Compilation Error Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.

Compiler Error Message: CS0006: Metadata file 'c:\windows\microsoft.net\framework\v1.1.4322\temporary asp.net files\expensereimbursment.gui\1512b04c\9c0cf0a7\ assembly\dl2\eafb3e9e\00cd9e21_48ffc401\sd.llblgen.pro.ormsupportclasses.net11.dll' could not be found

Now if I recompile again it will work. So basically I have to compile twice every time as I debug the app. I have tired removing and reading the reference to sd.llblgen.pro.ormsupportclasses.net11.dll but the problem still persists. I have been living with it for a couple of days now but I cannot take it any longer. I realize this is probably not a problem specific to llblgen but since it is an llblgen assembly I thought that I would trying posting here. Anybody have any ideas?

I can imagine it can be a real pain...

It could be that because of the strong named assembly that it's bugging. If you compile the ORMSUpportclasses library from the sourcecode using the makefile (remove the strong name from teh assemblyinfo.cs) which you can run on the command line after typing vsvars32.bat and then run the make11.cmd file, does it help?

Googling on the error, I find that having this tag: <identity impersonate="true" />

in the web.config could be the problem, do you have that tag? (google on:Compiler Error Message: CS0006: )

I do have the <identity impersonate="true" /> tag (have to impersonate a user with access to active directory to do AD authentication). Unfortunately, it looks as though this bug has no solution. Guess I will just have to put up with it. At least I know what the problem is. Thanks for your help!

Sam wrote:

I do have the <identity impersonate="true" /> tag (have to impersonate a user with access to active directory to do AD authentication). Unfortunately, it looks as though this bug has no solution. Guess I will just have to put up with it. At least I know what the problem is. Thanks for your help!

Does the unsigned version of the runtime library (which you can compile yourself) solve the problem?.