Skip to content
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

.Net core 3 support #686

Merged
merged 17 commits into from
Dec 9, 2019
Merged

Conversation

ProH4Ck
Copy link
Contributor

@ProH4Ck ProH4Ck commented Sep 25, 2019

This let it works with a .net core 3 project and solves:

System.TypeLoadException: 'Could not load type 'Microsoft.AspNetCore.Mvc.MvcJsonOptions' from assembly 'Microsoft.AspNetCore.Mvc.Formatters.Json, Version=3.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'.'

@CLAassistant
Copy link

CLAassistant commented Sep 25, 2019

CLA assistant check
All committers have signed the CLA.

@ProH4Ck
Copy link
Contributor Author

ProH4Ck commented Oct 11, 2019

@rasmus I think build is blocked by some variables set on your AppVeyor account (relative to SQL Server).
The same build is working fine in my AppVeyor account: https://ci.appveyor.com/project/ProH4Ck/eventflow/builds/28040687

@ProH4Ck ProH4Ck changed the title WIP: .Net core 3 support .Net core 3 support Oct 16, 2019
@i-dentify
Copy link
Contributor

Any updates on this? I am soooo soooo waiting for this merge

@ProH4Ck
Copy link
Contributor Author

ProH4Ck commented Nov 8, 2019

Any updates on this? I am soooo soooo waiting for this merge

I can't do anything... Build is working fine on my appveyor account. @rasmus we need you!

IConfigureOptions<MvcJsonOptions>
#endif
#if NETCOREAPP3_0
IConfigureOptions<MvcNewtonsoftJsonOptions>
Copy link
Contributor

@leotsarev leotsarev Nov 29, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that using ASP.NET Core 2.1 on .NET Core is possible. This scenario will fail, won't it?

twzhangyang pushed a commit to twzhangyang/RestAirline that referenced this pull request Dec 1, 2019
waiting for eventflow merge below request:eventflow/EventFlow#686
@rasmus
Copy link
Member

rasmus commented Dec 3, 2019

Hi @ProH4Ck thanks for the PR, but it seems like the integration tests for MSSQL and EF are broken though.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connection

👍 for moving the integration test setup to the official images!

@ProH4Ck
Copy link
Contributor Author

ProH4Ck commented Dec 4, 2019

Hi @ProH4Ck thanks for the PR, but it seems like the integration tests for MSSQL and EF are broken though.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connection

👍 for moving the integration test setup to the official images!

Hi @rasmus
they're failing because probably you have ms sql connection string hard coded in your appveyor account.
The same build is working fine on my appveyor:
https://ci.appveyor.com/project/ProH4Ck/eventflow/builds/28040687

I have no variables set in my account:

image

I tried to move sql server to docker but memory limits on appveyor prevent container to start...

@Brandon2255p
Copy link

Dotnet core 2.2 is reaching its end of life by the end of this year.
Could @rasmus please outline what is outstanding? I am going to work to push this PR over the line :)

@rasmus
Copy link
Member

rasmus commented Dec 9, 2019

@Brandon2255p I'm going through the settings and everything seems to be as should be.

My wife has started evening school which means I don't have as much time for spare time projects as I would like, as I have the kids full time. I do try to keep up, but I'll try to be more available.

@rasmus
Copy link
Member

rasmus commented Dec 9, 2019

I'll see if I can do a separate update of the image to 2019 tonight, removing the need for it in this PR.

@rasmus rasmus mentioned this pull request Dec 9, 2019
@rasmus
Copy link
Member

rasmus commented Dec 9, 2019

I'll try to get the image change working in #709

rasmus pushed a commit that referenced this pull request Dec 9, 2019
@rasmus
Copy link
Member

rasmus commented Dec 9, 2019

Found the problem in #709, will hopefully get it merged tonight. If it does, I'll merge develop into this PR as well to see if fixes the build here as well.

@rasmus rasmus merged commit 578b2dc into eventflow:develop Dec 9, 2019
@i-dentify
Copy link
Contributor

Found the problem in #709, will hopefully get it merged tonight. If it does, I'll merge develop into this PR as well to see if fixes the build here as well.

Hooray!

@Brandon2255p
Copy link

Brandon2255p commented Dec 9, 2019 via email

@rasmus
Copy link
Member

rasmus commented Dec 9, 2019

@Brandon2255p just keep poking me if I don't respond. Its my responsibility and I need to make the time.

There's a problem with the license in several of the source files (not from this PR). Basically the header isn't correct in accordance to the CLA. I'm correcting this in #712 and will release as soon as its done.

I try to keep the legal stuff correct, but darn its hard.

@ProH4Ck
Copy link
Contributor Author

ProH4Ck commented Dec 10, 2019

Finally merged! Thanks!
Maybe it's time for 1.0.0 release?

@ProH4Ck ProH4Ck deleted the feature/netcore3-update branch December 10, 2019 07:30
@promontis
Copy link
Contributor

@rasmus awesome! Thanks for the great work! Is there already a new NuGet release for this?

@rasmus
Copy link
Member

rasmus commented Dec 10, 2019 via email

@promontis
Copy link
Contributor

@rasmus take your time :) no need to rush

@rasmus
Copy link
Member

rasmus commented Dec 10, 2019

@promontis managed to get out of bed and start the release. You can follow it here

https://ci.appveyor.com/project/eventflow/eventflow/builds/29444767

I'll check on it in a few hours to see if everything is ok. The GitHub release draft with artifacts needs to be published manually, but the NuGet packages will be uploaded during the build. As soon as NuGet then indexes the packages, you should be able to upgrade.

@promontis
Copy link
Contributor

It's up \o/ \o/ \o/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants