Skip to content
This repository has been archived by the owner on Dec 3, 2019. It is now read-only.

Handling optional project ref in .sln files? #38

Open
jdkang opened this issue Oct 25, 2018 · 0 comments
Open

Handling optional project ref in .sln files? #38

jdkang opened this issue Oct 25, 2018 · 0 comments

Comments

@jdkang
Copy link

jdkang commented Oct 25, 2018

I'm looking to use dotnet new to help template both old VS solutions and new dotnet type projects.

See also: VS Solution File

When manipulating an .sln for inclusion of OPTIONAL projects (i.e. giving the user the option for sub projects such as Foo.Data/Foo.Data.csproj) the .sln file would need its references updated/omitted.

In yeoman/npm

In yeoman/npm this is handled with inline code.

	GlobalSection(ProjectConfigurationPlatforms) = postSolution<% for(var project in projects) { %>
		{<%= projects[project].projectGuid %>}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
		{<%= projects[project].projectGuid %>}.Debug|Any CPU.Build.0 = Debug|Any CPU
		{<%= projects[project].projectGuid %>}.Release|Any CPU.ActiveCfg = Release|Any CPU
		{<%= projects[project].projectGuid %>}.Release|Any CPU.Build.0 = Release|Any CPU<% } %>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant