Exclude nested files from source control

[adam0101]

We're having a problem combining 'nested files' and excluding files from source control.

We're using code generation to create two partial classes for each entity - MyBusinessObject.vb and MyBusinessObject.Generated.vb

We'd like the "Generated" file to appear as a nested file under the manual file. So we're modifying the .vbproj project file to include entries like this:

<Compile Include="MyBusinessObject.vb" />
<Compile Include="MyBusinessObject.Generated.vb">
    <DependentUpon>MyBusinessObject.vb</DependentUpon>
</Compile>

This works fine by itself. Since we already have the code generation templates under source control, we'd also like to keep the "Generated" files out of source control so we only have to check out the project file to regenerate instead of everything. So we modified the .vbproj.vspscc project source control file like this:

{
"FILE_VERSION" = "9237"
"ENLISTMENT_CHOICE" = "NEVER"
"PROJECT_FILE_RELATIVE_PATH" = ""
"NUMBER_OF_EXCLUDED_FILES" = "1"
"EXCLUDED_FILE0" = "MyBusinessObject.Generated.vb"
"ORIGINAL_PROJECT_FILE_PATH" = ""
"NUMBER_OF_NESTED_PROJECTS" = "0"
"SOURCE_CONTROL_SETTINGS_PROVIDER" = "PROVIDER"
}

This also works fine by itself. The problem is when we combine these two processes, MyBusinessObject.vb shows as being excluded from source control even though it's not in the project source control file like MyBusinessObject.Generated.vb is.

Is it possible to have nested files and have the main file in source control and the nested file excluded from source control?

Thanks for your help!


Adam

http://adameslinger.blogspot.com/

 

[adam0101]

I ended up handling this a different way. If you're interested, here's what I did:

http://stackoverflow.com/questions/484795/exclude-nested-files-from-source-control