Anyone here using ASP.NET Core on .NET Framework?

[Spacerat]

I tried this but I cannot reference any of my existing assemblies. So it defeats the purpose a bit. I am using the latest tooling.

 

[[)roi(]]

I tried this but I cannot reference any of my existing assemblies. So it defeats the purpose a bit. I am using the latest tooling.

Are you referring to ASP.Net Core and .NET Core? and which platform?

 

[Spacerat]

Are you referring to ASP.Net Core and .NET Core? and which platform?

Yes, you can run ASP.NET Core on the Core Framework or the full .NET framework. I have a whole lot of other assemblies I need to reference because my WebAPI calls into several other APIs. So I created a test WebApi with .NET Core to run on .NET framework (options at creation time). But I cannot ref my other .NET 4.5.2 assy's. This used to be a bug in the tooling, but I now have latest version...

What I like about the ASP.NETCore, is that it is very lightweight. The idea is to host on AWS or Azure VM.

 

[[)roi(]]

Yes, you can run ASP.NET Core on the Core Framework or the full .NET framework. I have a whole lot of other assemblies I need to reference because my WebAPI calls into several other APIs. So I created a test WebApi with .NET Core to run on .NET framework (options at creation time). But I cannot ref my other .NET 4.5.2 assy's. This used to be a bug in the tooling, but I now have latest version...

Did you try targeting 4.5.2 directly? e.g. https://jonhilton.net/2016/09/07/using-asp-net-core-against-net-4-6/

 

[Spacerat]

Did you try targeting 4.5.2 directly? e.g. https://jonhilton.net/2016/09/07/using-asp-net-core-against-net-4-6/

Yes I rebuilt my other assy's to 4.5.2 and then targeted 4.5.2 in the ASP.NET Core app. No luck.

The main reason is am considering this is that the app was built around Firebird DB. Only way to host this on Azure or AWS is on a virgin VM. This means that I have to do all the IIS stuff. With ASP.NET Core you don't need to hassle with IIS. The WebAPI builds to a console app that you can just deploy and run.

The alternative is to migrate the app to MSSQL and then host as an app service with Azure SQL DB, which actually makes more sense. Although my ORM is DB agnostic, I was not looking fwd to migrating the DB. At least there is no data as it is a new app. So the latter is prob the way to go.

I was just looking for a quick win....

 

[[)roi(]]

Yes I rebuilt my other assy's to 4.5.2 and then targeted 4.5.2 in the ASP.NET Core app. No luck.

The main reason is am considering this is that the app was built around Firebird DB. Only way to host this on Azure or AWS is on a virgin VM. This means that I have to do all the IIS stuff. With ASP.NET Core you don't need to hassle with IIS. The WebAPI builds to a console app that you can just deploy and run.

The alternative is to migrate the app to MSSQL and then host as an app service with Azure SQL DB, which actually makes more sense. Although my ORM is DB agnostic, I was not looking fwd to migrating the DB. At least there is no data as it is a new app. So the latter is prob the way to go.

I was just looking for a quick win....

Most of the problems I experienced were resolved with either 3rd party support for Core frameworks, and in 2 cases targeting the 4.5 and 4.6 worked.

Also don't the crash reports at least pinpoint some underlying problem? Alternatively get in touch with an ASP.Net and/or .Net Core team member on twitter... some are quite helpful.

 

[Spacerat]

Most of the problems I experienced were resolved with either 3rd party support for Core frameworks, and in 2 cases targeting the 4.5 and 4.6 worked.

Also don't the crash reports at least pinpoint some underlying problem? Alternatively get in touch with an ASP.Net and/or .Net Core team member on twitter... some are quite helpful.

Will do tx

 

[oober]

In my opinion it's not ready for prime time. My experience was.

Not enough 3rd party library support.
Failed attempt at a project.json so later on you will have to go back to something else?
Lot's of fiddling with assembly bindings redirects.

Maybe for very simple sites it's ok?

Did you consider using OWIN to run your app in a console?

 

[DA-LION-619]

In my opinion it's not ready for prime time. My experience was.

Not enough 3rd party library support.
Failed attempt at a project.json so later on you will have to go back to something else?
Lot's of fiddling with assembly bindings redirects.

Maybe for very simple sites it's ok?

Did you consider using OWIN to run your app in a console?

One of their reasons for dumping project.json is that when they acquired Xamarin, Xamarin has 16 or 17 project types.

 

[Spacerat]

In my opinion it's not ready for prime time. My experience was.

Not enough 3rd party library support.
Failed attempt at a project.json so later on you will have to go back to something else?
Lot's of fiddling with assembly bindings redirects.

Maybe for very simple sites it's ok?

Did you consider using OWIN to run your app in a console?

Yes that is the conclusion I came to. Will def try OWIN as I'd rather now spend the time finalising the app than migrating the db