This is killing me

[The-Futurist]

I'm reading that I can create an ASP.NET Core wb app project that targets .Net Framework. However there have been numerous articles published over the past year that are either out of date or simply flat wrong.

One article said to edit the project.json file - then a little later I discover this is no longer used and we're back to good old *.csproj.

Anyway when I create a new ASP.NET Core web app I get no option to select a target framework (I've installed 2.1 too by the way).

Even after the project is created if I go to project properties then the Application pane the only options in Target framework dropdown list are .Net Core 1.0, 1.1, 2.0 and 2.1 - No sign anywhere of .Net Framework.

So perhaps one must manually edit the *.csproj file which is inexcusably sloppy if true.

I've said this before and so have others - this is a mess...

[davidfowl]

New Project -> Web -> ASP.NET Core Application:

.NET Framework:

Done

[The-Futurist]

@davidfowl - Except it's not "Done" in my case because the dropdown list is mysteriously and inexplicably disabled and says only ".NET Core" as you can see here:

[davidfowl]

What options did you select when you installed VS 2017?

/cc @Andrew-MSFT @BillHiebert

Any ideas?

[The-Futurist]

@davidfowl - I really can't recall, it was a year ago. Almost all work I do on this particular machine is conventional .NET Framework stuff MVC, desktop apps, console apps etc. I can certainly see the current setup of installed bits n pieces though if you want me to check something in particular.

[AndrewBrianHall]

The Target Framework dropdown will be locked to .NET Core if you enter through the ".NET Core" node in the new project dialog. If you enter through the "Web" entry point as shown in @davidfowl's screenshot, you will be able to choose between the two.

[The-Futurist]

@Andrew-MSFT @davidfowl - Thank you gentlemen, this is much appreciated!

[narendra2605]

@Korporal: But if you select ".Net Framework" from the 1st dropdown, you are creating a .Net Framework Web App and not a .Net Core WebApp targeting .Net Framework. Hope you get it.

[Plasma]

Thank you @davidfowl and @Korporal -- I had the exact same experience trying to get started porting a large ASP.NET MVC app to .NET Core, targeting .NET Framework (to assist with porting).

Would really like to see a more thorough guide, including things like how to upgrade old controllers, utilize existing route code, etc, as I think each person/team is struggling independently and it would be good to have a central location to document a good bunch of the steps.

Thank you

[davidfowl]

Would really like to see a more thorough guide, including things like how to upgrade old controllers, utilize existing route code, etc, as I think each person/team is struggling independently and it would be good to have a central location to document a good bunch of the steps.

https://docs.microsoft.com/en-us/aspnet/core/migration/proper-to-2x/?view=aspnetcore-2.1

Provide feedback on that document.