.NET Core templates?

Elements
, ,
41

Sample project: NetCoreApplication286.zip (37.9 KB)

What should work in .2299:

  • build
  • run manually with “dotnet exec”
  • run w/o debugging (Fire, Water)
  • run in debugegr\ (VS, Water)
  • Configure SDK & Runtime, including version, in project settings (Fire, Water)

What’s missing/coming in .2301 next week:

  • you can remove the explicit Microsoft.NETCore.App reference as that will be added automatically, in the next build
  • .NET Core debugging on Mac, in Fire.
  • templates
42

What should work in .2299:

What’s missing/coming in .2301 next week:

Why only uneven build numbers?

43

We ship uneven build numbers, and build even builds internally. Eg this morning in increased the build no to 2299, and we did the build we shipped. Then the. build number was set to 2300. There’ll be dozens of builds done internally over there next week, all versioned 2300. When we’re ready to ship the next build, we go to 2301, and the cycle repeats.

This way, all builds that leave the house (aside form off-shots we send to individual people for retesting specific fixes) have a unique build number, but on the flip Sid,e build numbers stay sane — if we’d increase with every build we do, we’d be in the 6+ digits now…

44

Because of this, a new build, .2301, is up now, and it happens to also include the following changes, already:

45

Hi, any news for ASP.NET Core templates?

46

ASP, no. Regular Core should be fully supported now, ASP.NET is next on my list, in that area.