Archived Support Site

This support site is archived. You can view the old support discussions but you cannot post new discussions.

AppHarbor - ASP.Net 5 / vNext Support

yngndrw's Avatar

yngndrw

05 May, 2015 03:53 PM

Does AppHarbor support ASP.Net 5 / vNext ?

When I tried to deploy my sample application (From the Visual Studio 2015 RC templates) I got the following build log in AppHarbor:

Build started 5/4/2015 2:28:38 PM.
     1>Project "D:\temp\g3zdb4oh.rcv\input\ASPNetTest.sln" on node 1 (default targets).
     1>ValidateSolutionConfiguration:
         Building solution configuration "Release|Any CPU".
     1>Project "D:\temp\g3zdb4oh.rcv\input\ASPNetTest.sln" (1) is building "D:\temp\g3zdb4oh.rcv\input\src\ASPNetTest\ASPNetTest.xproj" (2) on node 1 (default targets).
     2>D:\temp\g3zdb4oh.rcv\input\src\ASPNetTest\ASPNetTest.xproj(7,3): error MSB4019: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\DNX\Microsoft.DNX.Props" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
     2>Done Building Project "D:\temp\g3zdb4oh.rcv\input\src\ASPNetTest\ASPNetTest.xproj" (default targets) -- FAILED.
     1>Done Building Project "D:\temp\g3zdb4oh.rcv\input\ASPNetTest.sln" (default targets) -- FAILED.

Build FAILED.

       "D:\temp\g3zdb4oh.rcv\input\ASPNetTest.sln" (default target) (1) ->
       "D:\temp\g3zdb4oh.rcv\input\src\ASPNetTest\ASPNetTest.xproj" (default target) (2) ->
         D:\temp\g3zdb4oh.rcv\input\src\ASPNetTest\ASPNetTest.xproj(7,3): error MSB4019: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\DNX\Microsoft.DNX.Props" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.

    0 Warning(s)
    1 Error(s)

Time Elapsed 00:00:00.03

The code that I tried to deploy was this: https://github.com/yngndrw/ASPNetTest

I'm not sure if I missed something or if AppHarbor doesn't support this yet ?

Thanks,
-Andrew.

  1. 1 Posted by yngndrw on 05 May, 2015 03:55 PM

    yngndrw's Avatar
  2. 2 Posted by OliPicard on 07 May, 2015 07:58 PM

    OliPicard's Avatar

    I'm hoping AH will include support for 4+ and 5+ as 4+ is the last version to include webforms (a buildout that uses legacy webforms)

    Would be good to get support fro AH on this, Lots of developers need time to port over to MVC if at all.

  3. Support Staff 3 Posted by rune on 07 May, 2015 08:19 PM

    rune's Avatar

    Hi,

    ASP.NET 5 / vNext and .NET 4.6 is not officially supported yet as they are still at the RC state - official support will be rolled out and deployed across all servers when they reach RTM. Note however that for vNext / ASP.NET 5 application you may still be able to run those applications on AppHarbor, but for now you'd have to work around the missing build targets projects, as those are not currently available on AppHarbor's build servers.

    AppHarbor will continue to support earlier versions of the .NET Framework including 4+, and there are no plans to discontinue support for applications requiring those frameworks when vNext and .NET 4.6 is officially supported.

    We may also introduce beta support or guidelines for deploying apps using the newer frameworks prior to the official RCs. I'll make sure to update this thread if/when we do this.

    Best,
    Rune

  4. 4 Posted by yngndrw on 07 May, 2015 09:14 PM

    yngndrw's Avatar

    Thank you very much for the response Rune, that's most helpful. I look forward to seeing how the ASP.Net 5 development unfolds and the opportunities it unlocks. I'm also hoping to see a new set of Mono-based hosting packages available with lower pricing, but we'll have to wait to see how that all unfolds.

    @OliPicard: In my opinion, even if hypothetically speaking official support for webforms was to be dropped, there are so many people who still depend on it that somebody would write some from of adapter to run legacy webforms web applications on ASP.Net 5. I don't think there's anything to worry about for a while yet.

  5. 5 Posted by EricMKaufman on 24 Jul, 2015 01:43 PM

    EricMKaufman's Avatar

    Any update on support for .NET 4.6 and C#6?

  6. Support Staff 6 Posted by rune on 26 Jul, 2015 03:42 PM

    rune's Avatar

    Hi,

    The build and application servers were upgraded last week to support .NET 4.6, Roslyn, Typescript 1.5 and more, so you should be able to run apps targeting/using these already.

    We're making a few changes to the build process to better support ASP.NET 5/vNext apps and plan to roll the updated setup out over the next week, but if you just need .NET 4.6 features you can start using that already. Let me know if you hit any snags!

    Best,
    Rune

  7. 7 Posted by nsyed on 31 Aug, 2015 03:51 AM

    nsyed's Avatar

    May i know what is the work around to make work aspnet 5 applications,
    and also when this will be supported

  8. 8 Posted by Alexander Oryol on 11 Oct, 2015 08:25 PM

    Alexander Oryol's Avatar

    So, are you going to oficially support dnx/xproj deployment? If yes, when we can expect it?

  9. Support Staff 9 Posted by rune on 14 Oct, 2015 10:57 PM

    rune's Avatar

    Hi,

    Sorry about the slow response here. The plan is to officially support ASP.NET 5/dnx/vNext apps when they graduate from beta. We may still add experimental support prior to that, but I can't give you a firm timeline for this - vNext is still under heavy development and it's a bit of a moving target for the same reason. Few people use it for stable production apps (which remain our focus), but it'd be great to test and play around with prior to RTM. I'll make sure to ping you guys as soon as we start testing this in public/private beta.

    Best,
    Rune

  10. rune closed this discussion on 14 Oct, 2015 10:57 PM.

Discussions are closed to public comments.
If you need help with AppHarbor please start a new discussion.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac