AMT-Cheif
/
Stylet
mirror of https://github.com/AMT-Cheif/Stylet.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Stylet/Stylet.sln

38 lines
2.1 KiB
Plaintext
Raw Normal View History

Split Stylet and IntegrationTests projects into Framework and Core Annoyingly we need to have two separate projects in two separate directories, since Framework WPF projects aren't supported in sdk-style csprojs. The Framework and Core projects also stamp over each others' bin and obj directories, even if you set IntermediateFilePath, hence the need to put them in entirely separate places
2019-07-05 05:14:38 -07:00

Microsoft Visual Studio Solution File, Format Version 12.00
# Visual Studio Version 16
VisualStudioVersion = 16.0.29021.104
MinimumVisualStudioVersion = 10.0.40219.1
Turns out it is possible to have a single csproj targetting both core and framework <EnableDefaultItems>false</EnableDefaultItems> along with <Compile Include="**\*.cs" Exclude="obj\**" /> and <None Remove="**\*.cs" /> is needed, though.
2019-09-22 06:39:46 -07:00
Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "StyletUnitTests", "StyletUnitTests\StyletUnitTests.csproj", "{13AFA20D-CCEA-4A58-920E-4D8816C7296B}"
Split Stylet and IntegrationTests projects into Framework and Core Annoyingly we need to have two separate projects in two separate directories, since Framework WPF projects aren't supported in sdk-style csprojs. The Framework and Core projects also stamp over each others' bin and obj directories, even if you set IntermediateFilePath, hence the need to put them in entirely separate places
2019-07-05 05:14:38 -07:00
EndProject
Turns out it is possible to have a single csproj targetting both core and framework <EnableDefaultItems>false</EnableDefaultItems> along with <Compile Include="**\*.cs" Exclude="obj\**" /> and <None Remove="**\*.cs" /> is needed, though.
2019-09-22 06:39:46 -07:00
Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "Stylet", "Stylet\Stylet.csproj", "{895A0541-84CF-4D3D-9539-58F1FC286336}"
Split Stylet and IntegrationTests projects into Framework and Core Annoyingly we need to have two separate projects in two separate directories, since Framework WPF projects aren't supported in sdk-style csprojs. The Framework and Core projects also stamp over each others' bin and obj directories, even if you set IntermediateFilePath, hence the need to put them in entirely separate places
2019-07-05 05:14:38 -07:00
EndProject
Turns out it is possible to have a single csproj targetting both core and framework <EnableDefaultItems>false</EnableDefaultItems> along with <Compile Include="**\*.cs" Exclude="obj\**" /> and <None Remove="**\*.cs" /> is needed, though.
2019-09-22 06:39:46 -07:00
Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "StyletIntegrationTests", "StyletIntegrationTests\StyletIntegrationTests.csproj", "{4122F924-6B71-4DDA-995E-FAF78242E20C}"
Split Stylet and IntegrationTests projects into Framework and Core Annoyingly we need to have two separate projects in two separate directories, since Framework WPF projects aren't supported in sdk-style csprojs. The Framework and Core projects also stamp over each others' bin and obj directories, even if you set IntermediateFilePath, hence the need to put them in entirely separate places
2019-07-05 05:14:38 -07:00
EndProject
Global
GlobalSection(SolutionConfigurationPlatforms) = preSolution
Debug|Any CPU = Debug|Any CPU
Release|Any CPU = Release|Any CPU
EndGlobalSection
GlobalSection(ProjectConfigurationPlatforms) = postSolution
{13AFA20D-CCEA-4A58-920E-4D8816C7296B}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
{13AFA20D-CCEA-4A58-920E-4D8816C7296B}.Debug|Any CPU.Build.0 = Debug|Any CPU
{13AFA20D-CCEA-4A58-920E-4D8816C7296B}.Release|Any CPU.ActiveCfg = Release|Any CPU
{13AFA20D-CCEA-4A58-920E-4D8816C7296B}.Release|Any CPU.Build.0 = Release|Any CPU
Turns out it is possible to have a single csproj targetting both core and framework <EnableDefaultItems>false</EnableDefaultItems> along with <Compile Include="**\*.cs" Exclude="obj\**" /> and <None Remove="**\*.cs" /> is needed, though.
2019-09-22 06:39:46 -07:00
{895A0541-84CF-4D3D-9539-58F1FC286336}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
{895A0541-84CF-4D3D-9539-58F1FC286336}.Debug|Any CPU.Build.0 = Debug|Any CPU
{895A0541-84CF-4D3D-9539-58F1FC286336}.Release|Any CPU.ActiveCfg = Release|Any CPU
{895A0541-84CF-4D3D-9539-58F1FC286336}.Release|Any CPU.Build.0 = Release|Any CPU
{4122F924-6B71-4DDA-995E-FAF78242E20C}.Debug|Any CPU.ActiveCfg = Debug|Any CPU
{4122F924-6B71-4DDA-995E-FAF78242E20C}.Debug|Any CPU.Build.0 = Debug|Any CPU
{4122F924-6B71-4DDA-995E-FAF78242E20C}.Release|Any CPU.ActiveCfg = Release|Any CPU
{4122F924-6B71-4DDA-995E-FAF78242E20C}.Release|Any CPU.Build.0 = Release|Any CPU
Split Stylet and IntegrationTests projects into Framework and Core Annoyingly we need to have two separate projects in two separate directories, since Framework WPF projects aren't supported in sdk-style csprojs. The Framework and Core projects also stamp over each others' bin and obj directories, even if you set IntermediateFilePath, hence the need to put them in entirely separate places
2019-07-05 05:14:38 -07:00
EndGlobalSection
GlobalSection(SolutionProperties) = preSolution
HideSolutionNode = FALSE
EndGlobalSection
GlobalSection(ExtensibilityGlobals) = postSolution
SolutionGuid = {6A75A07E-E87F-4A90-BA14-D1237C7A3C67}
EndGlobalSection
EndGlobal