You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 3, 2019. It is now read-only.
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<% } %>
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 asFoo.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.
The text was updated successfully, but these errors were encountered: