Hello,

I am using VS 2003, and have both LLBLGen 1.1 and LLBLGen 2.0 installed.

It appears as though Visual Studio is getting confused between the new DLLs and the old DLLs -- whenever I build, the LLBLGen projects re-set the references from the 2.0 DLLs to the 1.1 DLLs (SD.LLBLGen.Pro.ORMSupportClasses.NET11.dll and SD.LLBLGen.Pro.DQE.SqlServer.NET11.dll); that is, the correct DLLs are being referenced, but from the 1.1 directory rather than the 2.0 directory -- even though I set them to the 2.0 directory, whenever I build, they get set to the 1.1 directory again.

Is there a way to fix this (without uninstalling LLBLGen 1.1)?

EDIT: I have been having a hard time replicating this problem... It does not seem to happen every time I build, and it does not seem to happen every time i regenerate the LLBLGen code -- Unfortunately, since I cannot replicate the problem, I'm not sure about the cause anymore

Are you setting the references using the direct file or the GAC?

Check out your references path (Project/Properties/References Path) order. When assemblies aren't loaded from GAC those path are used in DESC order to find the assemblies by file name.

IMHO a vs.net problem. It could be solved by first removing all references, save the solution, close vs.net, deleting the .suo and .user files from the code folders as these contain the references. Then also remove the obj folders and then start vs.net 2003 again, load solution and assign all references again. But it could be that less drastic actions like simply removing the obj folders also works. What's odd is that it sometimes works... Do you share the code with someone else (via sourcecontrol) ?

Smells like a VS.NET problem to me too. 2003 has these issues a LOT in my experience, at least in a multiple-developer environment. 2005 seems to be much better BTW. Is your solution under version control?

I suspect it's a VS.NET problem as well... and no, the project is not under source control.

I'll try the solutions you guys suggested.

What I found works is if I build, and the errors occur, I build again, and it's fine (builds without errors).