corrade-vassal

Subversion Repositories:
Compare Path: Rev
With Path: Rev
?path1? @ 5  →  ?path2? @ 6
/Vassal/Vassal/Vassal.csproj
@@ -106,6 +106,9 @@
<None Include="Regions.csv">
<CopyToOutputDirectory>Always</CopyToOutputDirectory>
</None>
<None Include="Vassal.exe.config">
<CopyToOutputDirectory>Always</CopyToOutputDirectory>
</None>
<None Include="Vassal.ini">
<CopyToOutputDirectory>Always</CopyToOutputDirectory>
</None>
@@ -119,6 +122,9 @@
<ItemGroup>
<Content Include="Vassal.ico" />
</ItemGroup>
<ItemGroup>
<Folder Include="libs\" />
</ItemGroup>
<Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" />
<!-- To modify your build process, add your task inside one of the targets below and uncomment it.
Other similar extension points exist, see Microsoft.Common.targets.
/Vassal/Vassal/Vassal.exe.config
@@ -0,0 +1,22 @@
<configuration>
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5"/>
</startup>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<probing privatePath="libs"/>
</assemblyBinding>
<!--
You can enable only one of these settings by commenting them out.
As a quick rule: server garbage collection uses up more memory
in favor of less CPU consuption and concurrent garbage collection
uses up more CPU in favour of memory consuption.
The default is to let the runtime pick a good choice for the machine.
-->
<!--
<gcConcurrent enabled="false"/>
<gcServer enabled="true"/>
-->
</runtime>
</configuration>