1. 07 5月, 2017 1 次提交
  2. 26 3月, 2017 1 次提交
    • N
      VS 2017 .csproj Migration · ae7a29a9
      Nick Craver 提交于
      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