Home → Support →

.Net core - MSB4019: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\DotNet\Microsoft.DotNet.Props" was not found.

• Edit

jhoppe

23 May, 2016 01:18 PM

Following up on the status of .net core support:

1) I see some posts stating that AppHarbor won't support .net core until it is out of beta. I assume that means RTM, not RC?

2) Any update since May 19? https://support.appharbor.com/discussions/problems/81426-any-updates-regarding-aspnet-5-support

3) I've also seen some posts mentioning that it may be possible, but you would have to work around the missing build target framework. I tried to build an app HoppeS.apphb.com and receiving the following:

MSBuild auto-detection: using msbuild version '14.0' from 'C:\Program Files (x86)\MSBuild\14.0\bin'. Use option -MSBuildVersion to force nuget to use a specific version of MSBuild. MSBuild P2P timeout [ms]: 120000 D:\temp\ddramvop.u4q\input\BlogServices\BlogServices.xproj(7,3): error MSB4019: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\DotNet\Microsoft.DotNet.Props" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.

System.AggregateException: One or more errors occurred. ---> NuGet.CommandLineException at NuGet.CommandLine.MsBuildUtility.GetProjectReferences(String msbuildDirectory, String[] projectPaths, Int32 timeOut) at NuGet.CommandLine.RestoreCommand.DetermineRestoreInputs() at NuGet.CommandLine.RestoreCommand.d__23.MoveNext() --- End of inner exception stack trace --- at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions) at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken) at NuGet.CommandLine.Command.Execute() at NuGet.CommandLine.Program.MainCore(String workingDirectory, String[] args) ---> (Inner Exception #0) NuGet.CommandLineException at NuGet.CommandLine.MsBuildUtility.GetProjectReferences(String msbuildDirectory, String[] projectPaths, Int32 timeOut) at NuGet.CommandLine.RestoreCommand.DetermineRestoreInputs() at NuGet.CommandLine.RestoreCommand.d__23.MoveNext()<---

Any advice on how to get started working around this? I suppose I could include the .net core SDK in my repository, but I don't know how I would let msbuild to know where to find it.

1. Support Staff 1 Posted by rune on 25 May, 2016 03:52 AM

   

   Hi there,

   1. Yes support is scheduled for release shortly after the RTM release of .NET Core. Now that we have the RC2 though work has started to integrate this as the API and configuration seems more solid at this time.
      
   2. Not at this time.
      
   3. You may be able to get it up and running with RC1, but RC2 introduced changes to the way IIS is configured with the new project types. In particular, the HttpPlatformHandler module integration in IIS has been replaced with a new AspNetCoreModule that'll require updates to the application servers, so it's unlikely that you'll be able to get this up and running with RC2 right now.

   Since the tooling is still in preview these have not been installed on the build servers, so that's why you're seeing the NuGet restore exception you included in this ticket.

   The current plan is to roll out an update the application server stack with preliminary support for the new AspNetCoreModule as part of the regular update schedule (i.e. most likely next patch Tuesday). That should enable you to test RC2, but with limited tooling support until we have production quality tools.

   I hope you can be patient while we work through the remaining changes required -- the priority is always to ensure a stable, production friendly platform that doesn't break across updates, and that's the primary reason support hasn't been introduced yet. Seems like we're getting pretty close to the final structure, configuration and tooling for the new dotnet frameworks and features, so shouldn't be long until we can officially support this.

   Best,
   Rune

   • Edit

2. 2 Posted by jhoppe on 25 May, 2016 07:13 PM

   

   Hi Rune,

   I had been curious about the potential workaround you hinted at for #3. Your explanation makes sense though. I'll put my RC2 code on Azure for now.

   Thank you for the update!

   Joe

   • Edit

3. 3 Posted by jhoppe on 20 Jul, 2016 03:57 PM

   

   Any update on support for .net core? Will there be a blog post when core is supported?

   Thanks,
   Joe

   • Edit

4. Support Staff 4 Posted by rune on 23 Jul, 2016 03:55 AM

   

   Hi Joe,

   This is going to take a bit longer than I was hoping for. .NET Core RTM has been released, but the tooling is not ready at all - in particular there will be significant changes to the way these apps are structured with the announced migration from project.json. Until we have a stable project structure it's going to be difficult to introduce full support, and I honestly wouldn't recommend creating production apps using these new features just yet. Chances are that a lot of changes will be required when the tooling and project structure is ready for prime time.

   That being said the AspNetCoreModule that is required to run .NET Core apps has already been installed on the application servers. This essentially means that users can already run these apps, but the application packages should not rely on tooling or other preinstalled components on the build servers - the app should be ready to deploy "as-is" rather than relying on build server components. This is also being used internally now for testing support on the worker servers. Apps currently need to follow a pretty specific layout and configuration for this to work, but I'll try and find time to put together a sample that can be used as a starting point until we have build server/CI support in place.

   In any case, yes there will be a blog post when support is introduced for these project types :-)

   Best,
   Rune

   • Edit

5. 5 Posted by ramin on 22 Oct, 2016 05:43 PM

   

   Hi.
   .net core RTM was released.
   when you support .net core.

   • Edit

6. Support Staff 6 Posted by rune on 25 Oct, 2016 10:13 PM

   

   Hi,

   We actually support .NET Core already, but the tooling is missing as it's still in preview (i.e. not even a beta) -- we're investigating ways to introduce this on the build servers without potentially affecting build processing for other apps (as it seems that the SDK may not reach RTM until next year).

   Also take a look at this discussion for a more recent update and steps to deploy .NET Core apps on AppHarbor today!

   Best,
   Rune

   • Edit

7. rune closed this discussion on 25 Oct, 2016 10:13 PM.