• Nick Craver's avatar
    VS 2017 .csproj Migration · ae7a29a9
    Nick Craver authored
    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
    ae7a29a9
Name
Last commit
Last update
Dapper Loading commit data...
Dapper.Contrib Loading commit data...
Dapper.EntityFramework Loading commit data...
Dapper.Rainbow Loading commit data...
Dapper.SqlBuilder Loading commit data...
Dapper.Tests Loading commit data...
Dapper.Tests.Contrib Loading commit data...
Dapper.Tests.Performance Loading commit data...
docs Loading commit data...
.gitattributes Loading commit data...
.gitignore Loading commit data...
Dapper.sln Loading commit data...
Dapper.sln.DotSettings Loading commit data...
Dapper.snk Loading commit data...
Directory.build.props Loading commit data...
License.txt Loading commit data...
Readme.md Loading commit data...
appveyor.yml Loading commit data...
build.ps1 Loading commit data...
build.sh Loading commit data...
game Loading commit data...