views:

413

answers:

1

Hey all,

I'm working on a Visual Studio template where the generated project relies on a number of references, which happen to be other projects under source control.

The question is how do I set this up in my ProjectGroup template? For example, if I have an already existing project at "C:\Stuff\MyUtilityProject\Utility.csproj" with a single file (Tools.cs) that I want to add to my template, how would I go about this?

Here's what my vstempalte looks like. FYI - I am having no issues with the ProjectTemplateLink or creation of the Solution folder, just in adding the pre-existing Utility.csproj to my new solution:

Thanks in advance!

<VSTemplate Version="2.0.0" xmlns="http://schemas.microsoft.com/developer/vstemplate/2005" Type="ProjectGroup">
  <TemplateData>
    <Name>MySampleSolution</Name>
    <Description>My Test Project</Description>
    <ProjectType>CSharp</ProjectType>
    <Icon>__TemplateIcon.ico</Icon>
  </TemplateData>
  <TemplateContent>
        <ProjectCollection>
            <SolutionFolder Name="Content">
                <Project File="C:\Stuff\MyUtilityProject\Utility.csproj">
                    <ProjectItem>Tools.cs</ProjectItem>
                </Project>
            </SolutionFolder>
        <ProjectTemplateLink ProjectName="MyWorkingTemplate">
            MyWorkingTemplate\MyTemplate.vstemplate
        </ProjectTemplateLink>
        </ProjectCollection>
  </TemplateContent>
</VSTemplate>
A: 

Hi,

Is this what you are looking for:

http://stackoverflow.com/questions/735715/visual-studio-programmatically-configure-solution-for-source-control

EDIT:

I have been looking around an seen this rather interesting project, it seems to export solutions rather than projects which may or may not be a better idea. I particularly like the part at the end that says it will strip out source control so you get a clean project. I know this is not the exact answer you would like but it is worth a look ;)

http://flux88.com/blog/exporting-visual-studio-solutions-with-solutionfactory/

DeanMc
Thanks for the reply, but not quite - we're looking to use an existing solution template vs. building this programatically.
Bob Palmer
Sorry my fault for not reading, there seems to be little on this about the web but I found a rather interesting project above that may be a step in the right direction, supports multiple projects and strips source control for output!
DeanMc
I actually looked at that one - the only sticking point is that it's fine if your template includes multiple new projects, but does not work if you need to reference existing projects - i.e. we have several solutions that all include a shared library project (not copies). Thanks!
Bob Palmer