I have been using LLBLGen for about a year on a project. We have two new developers working on this project now. We use the vault source control and have been running into problems when someone generates and checks in the generated project. When any other user does a get latest and retrieves all of the new projects their references to the vault break. The reference to the llblgen dal is made using a project reference. The project Guid changes, but the Package Guid stays the same. If the new user checks out one of these projects they can remove this reference and then add it, but when someone else gets the latest version their's breaks. Is there anything we should be doing differently to keep the Project Guid changing for these different versions of the generated code so that the references don't break when someone changes.

When you re-generate a project, don't throw the cs/vbproj files away, but make them writable (i.e. check them out). This will then make sure the project file generator will UPDATE the project file and keep the guid and the SAK references.

Then, after you've checked it back in, and some other person does getlatest or checks out the project, the file won't break, as the GUID stayed the same and teh proj file does have SAK references so sourcecontrol will work.

That worked great, thanks.