-
-
Notifications
You must be signed in to change notification settings - Fork 445
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove Paket and convert all projects to VS2017 format #324
Conversation
…rget framework to 4.6.2
Codecov Report
@@ Coverage Diff @@
## develop #324 +/- ##
===========================================
- Coverage 85.3% 83.03% -2.27%
===========================================
Files 242 242
Lines 5186 5182 -4
Branches 409 409
===========================================
- Hits 4424 4303 -121
- Misses 554 677 +123
+ Partials 208 202 -6
Continue to review full report at Codecov.
|
@ceferrari Impressive piece of work with some nice cleanup and as well 👍 👍 👍 A few initial comments
Let me know when its done |
Thank you @rasmus! You deserve all the recognition for this great project! The target framework is already reverted to v4.5.1.
Edit: I added a Task named "Restore" to build.cake file. It runs between "Version" and "Build" tasks and will show all restored packages. Is that what you mean by "see the resulting NuGet packages"? |
Thanks @ceferrari for that 😄 Regarding package you should update the Let me know if you need some feedback. |
@rasmus I had to convert all packages to the new .csproj (VS2017) format to make packaging work using the "DotNetCorePack" method from cake. I started with the root project (EventFlow) to make sure the subsequent projects did not have any duplicated references (e.g. If project A references Newtonsoft.Json and Project B references Project A, then Project B does not need to reference Newtonsoft.Json too, it will be transitive) I guess the packaging will be fine now but GitLink stopped working because it does not support the new .csproj format yet. I don't know what to do about it. The latest AppVeyor build failed because the MsSql tests failed. They shouldn't tho. If you can re-run they will probably pass. |
@ceferrari I re-run the build and it passed 👍 I created an issue at AppVeyor a few days back to get to the bottom of the SQL problem. They said this is an isolated case, so I'll look into that as soon as I get some time. It really cool that you did the switch to the new VS2017 project format as well as it should make it really easy to produce .NET standard packages (exchange The NuGet packages reference the project produced NuGet packages version Also the NuGet package is missing its details. NuGet.org takes the information from the packages, so if the information is removed, it will be removed from the site as well. NuGet packageDLL details for produced DLLsReference, NuGet package details downloaded from http://nuget.orgReference, DLL from NuGet downloaded from http://nuget.org |
@ceferrari Its a big change, but its looking good 👍 |
@rasmus The packages information are fixed now. Let me know if they match what is expected. |
Hi @ceferrari Again thanks for putting the work into this. A few minor comments.
As for the missing release notes within the NuGet packages details and breaking GitLink, well, I'll have a look at that at some later point. Getting this finalized is important. |
Hi @rasmus 1 - Done 2 - When I do that, the Owin tests fail. The relevant output from both "Ping" and "PublishCommand" tests is:
3 - Done I will keep an eye on GitLink updates to support the new .csproj files. |
@ceferrari Any last minute changes? If not I'll merge this in |
@rasmus No changes. Go ahead! |
@ceferrari Thanks, nice PR lost of good stuff 👍 |
Changed target framework to 4.6.2