I'm using Vault against LLBL generated projects. This is done so that if another programmer wants to check out the solution then he will get those projects.

When I regenerate my project I lose the following from my project file:

     <VisualBasic
        ProjectType = "Local"
        ProductVersion = "7.10.3077"
        SchemaVersion = "2.0"
        ProjectGuid = "{8E08E956-505B-4753-9F7F-52E0F890B8EA}"
        SccProjectName = "SAK"
        SccLocalPath = "SAK"
        SccAuxPath = "SAK"
        SccProvider = "SAK"
    >

I purge all the files prior to regeneration because it seems as though not all of the files get regenerated.

I'm using Adapter scenario (Full / Safe).

Am I doing this completly wrong?

Should I create a dll for the llbl projects and reference them in the solution as oppose to having the llbl projects in the solution?

Thanks,

One Confused Little Fishy

Fishy wrote:

I'm using Vault against LLBL generated projects. This is done so that if another programmer wants to check out the solution then he will get those projects.

When I regenerate my project I lose the following from my project file:

     <VisualBasic
        ProjectType = "Local"
        ProductVersion = "7.10.3077"
        SchemaVersion = "2.0"
        ProjectGuid = "{8E08E956-505B-4753-9F7F-52E0F890B8EA}"
        SccProjectName = "SAK"
        SccLocalPath = "SAK"
        SccAuxPath = "SAK"
        SccProvider = "SAK"
    >

I purge all the files prior to regeneration because it seems as though not all of the files get regenerated.

I'm using Adapter scenario (Full / Safe).

Am I doing this completly wrong?

Should I create a dll for the llbl projects and reference them in the solution as oppose to having the llbl projects in the solution?

Thanks,

One Confused Little Fishy

Hi, the SCC stuff is source control info that wouldn't be regenerated by LLBLGen Pro. The ProjectGUID is only used when the project participates in a Solution, which LLBLGen Pro doesn't provide either, if I remember correctly. I'm going to assume this applies to the other attributes as well.

All that being said, I personally just use file references to the generated assembly. Faster UI (I use VB), and less muss and fuss. I've been doing it that way for more than a year now.

Also, from a purist source control standpoint (if you're going to use file references), you should just store the .lgp file, the LLBLGen Pro binaries, and any modified templates, or custom code in source control and regenerate as needed. Keeping the final compiled code in binary form isn't bad either, but I don't think it's necessary to store all the generated source (the VS projects etc) unless there's a need for team development.

Jeff...

Thanks Jeff. Yea, the only reason it's in source control is for team development.

Fishy wrote:

I'm using Vault against LLBL generated projects. This is done so that if another programmer wants to check out the solution then he will get those projects.

When I regenerate my project I lose the following from my project file:

     <VisualBasic
        ProjectType = "Local"
        ProductVersion = "7.10.3077"
        SchemaVersion = "2.0"
        ProjectGuid = "{8E08E956-505B-4753-9F7F-52E0F890B8EA}"
        SccProjectName = "SAK"
        SccLocalPath = "SAK"
        SccAuxPath = "SAK"
        SccProvider = "SAK"
    >

I purge all the files prior to regeneration because it seems as though not all of the files get regenerated.

there's your error You should make the files writable. Then it's ok, as the proj file will then be updated, which keeps those SAK lines and the GUID. those things are important for VCC based sourcecontrol.