Support Hot Reload for ASP.NET Core for F#

[javiercn]

---

Issue moved from dotnet/aspnetcore#35824

• Please respond to @serefarikan.

---

From @serefarikan on Friday, August 27, 2021 10:29:22 AM

Is your feature request related to a problem? Please describe.

I'm using F# to develop REST APIS with asp.net core and I have to go through the build cycle to reflect changes to my server side logic, which costs time compared to what's available to other languages and frameworks.

Describe the solution you'd like

I'd like to have support for Hot Reload that is on its way to be introduced in Asp.NET Core 6.

Additional context

This feature is already supported for C# but F# support is described as :
F# is currently not supported in .NET 6 but we are planning to support in a future release based on customer feedback
https://devblogs.microsoft.com/dotnet/introducing-net-hot-reload

This the customer feedback.

[javiercn]

---

Issue moved from dotnet/aspnetcore#35824

• Please respond to @javiercn.

---

From @javiercn on Friday, August 27, 2021 10:48:59 AM

@serefarikan thanks for contacting us.

We are not aware of anything specific we need to do in ASP.NET Core to support hot reload with F#.

As far as I understand there are two levels for this:

• Compiler/IDE support (which we don't control)
• Framework support (which we control if you are using ASP.NET Core)
  • If you are using one of the F# specific frameworks for building Rest APIs, they might need to update stuff to get hot reload working.
  • WRT to ASP.NET Core hot reload, we should already have things in place independent of whether you are writing the app in C# or F#.

Given that we believe we are already doing everything we have to do at the framework level, I'm going to transfer this to the F# repo to let those folks chime in.

/cc: @pranavkm

@Pilchie feel free to loop in more folk if you have more context.

[ajeckmans]

See #11636 I guess

[serefarikan]

Thanks @ajeckmans , that looks like it.

[KevinRansom]

Thanks for providing this issue, we already have an issue covering this request,
Closing as a duplicate of: #11636