locked
Is there, or will there be support for .NET Core in Azure Cloud Services. RRS feed

  • Question

  • I have a Worker Role listening for TCP traffic in a worker role.  I developed it against 4.5.2, but would like to port it to .Net Core 2.2 if I can.  The .NET Core frameworks are not currently available for selection when creating a Cloud Service project.  Is it possible to use .NET Core, or has there been any indication that it will be available at any time? Thanks!!

    Sunday, February 17, 2019 4:53 AM

Answers

  • There is no ETA or plans I am aware of to support .NET Core in Cloud Services. Cloud Services is one of our classic products and new features are no longer being added. That being said, .NET core is something that is supported in Azure Web Apps or Service fabric for example. So you might consider going that route instead. 

    There has been no public discussions around what will be replacing cloud services in the future. Once that announcement/ decision has been made they will be sure to share supported languages and what not. 

    Tuesday, February 19, 2019 9:02 PM

All replies

  • There is no ETA or plans I am aware of to support .NET Core in Cloud Services. Cloud Services is one of our classic products and new features are no longer being added. That being said, .NET core is something that is supported in Azure Web Apps or Service fabric for example. So you might consider going that route instead. 

    There has been no public discussions around what will be replacing cloud services in the future. Once that announcement/ decision has been made they will be sure to share supported languages and what not. 

    Tuesday, February 19, 2019 9:02 PM
  • Thanks, Micah.  The big issue for me was being able to use ports other than 80and 443 and listen for TCP traffic.  My understanding was that Cloud Service Worker Roles were the only way to do this.  However ... I have started to look at IoT Hub and this may present the next best "replacement" for what I am currently doing and I could easily interact on the back end with my libraries ported to .NET Core.  Thanks again!!
    Thursday, February 21, 2019 10:03 AM