Home → Support →

Asp.Net 5 Support?

• Edit

Mahindar

15 Dec, 2015 06:14 PM

Hi,

When can we expect asp.net 5 support?

Thank you
Mahindar

1. Support Staff 1 Posted by rune on 17 Dec, 2015 04:51 PM

   

   Hi Mahindar,

   The software necessary to run ASP.NET/dnx/vNext apps is already in place, but support for the new project and solution types currently still needs to be added to make the build and deploy story smoother.

   ASP.NET 5 has been a bit of a moving target since it was introduced and we won't "officially" support it prior to 1.0.0.0/RTM, but now that we have the ASP.NET 5 RC 1 we have started working on that so official support can be added as soon as the RTM is released.

   In other words: You'll likely be able to run your ASP.NET 5 applications already, but some changes are necessary to make the process smoother. AppHarbor will officially support ASP.NET 5 when it's ready for production use. Linux support may be added in the future, but initially we'll start out with supporting it on Windows.

   On a related note: If you want to run Roslyn/C# 6.0 applications you might find this sample application useful. A few steps are necessary to configure the application and the commit history walks through those step by step.

   Even though ASP.NET 5.0 isn't officially supported yet you're of course still welcome to reach out if you're having trouble running those applications on AppHarbor.

   Best,
   Rune

   • Edit

2. 2 Posted by Mahindar on 17 Dec, 2015 04:58 PM

   

   Hi Rune,

   Thanks for the information. I will give it a try

   • Edit

3. 3 Posted by mkocaj on 01 Feb, 2016 09:32 AM

   

   re: https://support.appharbor.com/discussions/problems/77692-appharbor-...

   So we can deploy xproj web apps now?

   • Edit

4. Support Staff 4 Posted by rune on 07 Feb, 2016 01:30 AM

   

   Hi,

   The recent changes to the ASP.NET Core/vNext/DNX tooling has postponed this further -- we're waiting for the RC2 as there'll be some quite significant changes to the build and published tooling. You can read more about the changes in this blog post where the new roadmap is also mentioned.

   Best,
   Rune

   • Edit

5. rune closed this discussion on 07 Feb, 2016 01:30 AM.

6. Mahindar re-opened this discussion on 13 Aug, 2016 05:03 AM

7. 5 Posted by Mahindar on 13 Aug, 2016 05:03 AM

   

   Hi Rune,

   Is Asp.net Core project supported now? As Asp.net Core 1.0 is Released

   Thanks,
   Mahindar

   • Edit

8. Support Staff 6 Posted by rune on 16 Aug, 2016 01:24 AM

   

   Hi,

   .NET Core isn't fully supported just yet, but I do have a couple of updates to share:

   • The build servers have been updated to automatically copy the Roslyn binaries to the web project output directory if necessary. This render this manual step unnecessary.
   • The workers servers now have the .NET Core server hosting packages and the .NET Core runtime installed. We're holding back on adding the tooling/SDK to the build infrastructure for the time being as there are going be some pretty significant changes to this part (the SDK/CLI is still in preview and not ready for "prime time").

   Although the build servers don't currently support build/publishing Core apps you can still run .NET Core apps on AppHarbor today if you like -- you just need to publish it locally and upload the output to AppHarbor (for instance using the CLI). There are no special configuration required to get this up and running: Using a template VS2015 ASP.NET Core you can just run dotnet publish from the command line, go to the publish output directory and run appharbor deploy -a {your-app-name} to upload the artifact. Note however that configuration file replacement and logging isn't supported on the build servers. I expect that and full runtime support to be ready by the beginning of next month.

   Also, I suspect it may very well be possible to install and use the .NET Core SDK/CLI/tooling by using a solution file and MSBuild tasks. That way you might be able to use AppHarbor's existing build infrastructure to build and publish the project - at least for the time being while we wait for the pending .NET Core MsBuild integration.

   If you get a chance to try this and hit any snags I'd love to hear your feedback! Otherwise stay tuned for more updates on this developing story :-)

   Best,
   Rune

   • Edit

9. 7 Posted by Minh on 28 Sep, 2016 05:59 PM

   

   Hi rune,

   Do you have any update on this? How .NET Core is being support by Appharbor?

   Thank you,
   Minh

   • Edit

10. Support Staff 8 Posted by rune on 29 Sep, 2016 06:09 PM

    

    Hi Minh,

    The .NET Core SDK remain in preview, so the tooling is still missing on the build servers. The web servers have .NET Core installed though so you can still deploy and run .NET Core as mentioned above.

    I suspect it'd also be fairly straightforward to download the .NET Core SDK binaries only and include them with your repository -- a solution file could then execute the publish step with those binaries until the SDK is ready to be installed on the build servers.

    I'll follow up here when there are any updates regarding timeline to share, but rest assured that the development of the .NET Core SDK is being tracked closely and will most likely be available immediately after it graduates from preview/beta.

    Best,
    Rune

    • Edit

11. 9 Posted by Andras Sebo on 26 Oct, 2016 02:54 PM

    

    Hi,

    I've read this topic, but I still don't get it. I bound my appharbor application to my github source. Checked in and pushed the code, it appeared in appharbor, stopped with error due .net core error. Then I published locally (file system publish), but how do I copy those binaries into under my appharbor folder?

    Best,
    Andras

    • Edit

12. Support Staff 10 Posted by rune on 27 Oct, 2016 05:06 AM

    

    Hi Andras,

    Have you tried using the CLI as mentioned in the comment above?

    Best,
    Rune

    • Edit

13. rune closed this discussion on 14 Feb, 2017 11:56 PM.