VS 2017 .csproj Migration
Due to the way VS test works (by injecting an executable entry point), the performance tests needed to be factored out. I also organized all of our existing tests better along the way. Actual code changes to Dapper itself are very minor, only formatting and documentation fixes (which we need many more of). The build.ps1 script is upated to work, but note that <frameworkAssemblies> is not working in .nuspec inside the packages in the new .csproj system. I consider this to be a blocker. Issue is here: https://github.com/NuGet/Home/issues/4853
Showing
File deleted
File moved
File moved
Dapper.Tests/DecimalTests.cs
0 → 100644
Dapper.Tests/LiteralTests.cs
0 → 100644
Dapper.Tests/MiscTests.cs
0 → 100644
Dapper.Tests/TestBase.cs
0 → 100644
This source diff could not be displayed because it is too large. You can view the blob instead.
Dapper/Dapper.csproj
0 → 100644
Dapper/Dapper.xproj
deleted
100644 → 0
Dapper/project.json
deleted
100644 → 0
Directory.build.props
0 → 100644
NuGet.Config
deleted
100644 → 0
global.json
deleted
100644 → 0
tools/install.ps1
deleted
100644 → 0
tools/install.sh
deleted
100644 → 0
Please register or sign in to comment