Closed briansull closed 7 years ago
This looks like another ASP.NET breaking change, I'll fix it. I'm working on getting the dev
and rel/...
branches added to our CI so I can be notified about these things
If you want something stable, I'd recommend the rel/2.0.0-preview1
branch which uses a fixed set of ASP.NET libraries and the latest dotnet
CLI/SDK/Runtime
Looks like I missed the change to MusicStoreContext
in https://github.com/aspnet/MusicStore/commit/6c13465dc2018b59eef2edd93c7f6a39e8ec14a1
I looked over this commit when I saw it get merged to the MusicStore repo, and didn't catch this in with all of the changes that aren't relevant to JitBench.
It sounds like you will be checking a fix for this shortly. I rather continue working in the Dev branch as I need to collect profile data to use with future versions.
rel/2.0.0-preview1
works with the latest dotnet versions, do you mean you're tracking the ASP.NET changes specifically?
Fixed here: 94040906c1a7d8b2db373d63dc97910781e27eb3
@rynowak Reopen
Github has very simple rights/privileges (and even simpler management for them).
If you are not a collaborator of a repo, then (in regards to issues)
you can open issues you can comment on all existing issues (open or closed) you can close your own issues you can re-open your own issues *if you closed them yourself you cannot close or re-open issues opened by someone else you cannot re-open your own issues if a repo collaborator closed them
??? Are you saying this is still broken?
This is passing on travis and appveyor https://travis-ci.org/aspnet/JitBench/builds/238178713 https://ci.appveyor.com/project/aspnetci/jitbench/build/1.0.71
Yes, I was still getting those same two errors when building in the dev branch. I sounded like you checked on something to the wrong branch and then reverted it.
I checked it in to master and then reverted it there because master tracks 2.0.0-preview1.
The commit in dev is this one https://github.com/aspnet/JitBench/commit/94040906c1a7d8b2db373d63dc97910781e27eb3
If you're still having trouble I can stop by and take a look. This is working for me and in on the CIs.
OK It is fixed, I had a local change that was prevent me from pulling down your fix.
OK good, glad we got to the bottom of this.
I see that the build is currently flagged as being broken, but there is no issue or content in PR that explains what the current build break looks like, so I am adding this issue.
I am building a standalone version using "-r win10-x64" I get two compilation errors: