Does AppHarbor support ASP.NET Core?
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 ?
Rune from AppHarbor has responded to my question:
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
I will update further once support is added. Thanks.
Related
Trying to build a ASP.Net Core 1.0 project (.xproj) on a Build machine. Project built in VS2015. .Net Core is installed on the Build machine. I get this build error
The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\DotNet\Microsoft.DotNet.Props" was not found. Confirmed that path in the declaration is correct, and file exists on disk.
Tried the suggestion from this stackoverflow questionbut doesn't help.
I can confirm that the path and file do exist on the build server.
Also tried passing MS Build Argument /p:VisualStudioVersion=14.
Any leads highly appreciated.
Project Setup : Mixed framework solution
.Net Framework 4.6.2 projects in solution : 15
.Net Standard 2.0 projects in solution - 1
Development Machine
Visual Studio 2017(15.7.4) : Builds without any errors
Build Server
TeamCity Version 2017.1.3
Build Steps
Nuget Restore(3.4.4)
dotnet Restore
MSBuild( Build Tools 2017), Tools Version 15.0
Build fails with following error in the .net standard 2.0 project : [ResolvePackageAssets] C:\Program Files\dotnet\sdk\2.1.301\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.targets(198, 5): Package System.Security.Cryptography.ProtectedData, version 4.4.0 was not found. It might have been deleted since NuGet restore. Otherwise, NuGet restore might have only partially completed, which might have been due to maximum path length restrictions.
What's interesting is I can't find reference or use of System.Security.Cryptography.ProtectedData anywhere in the project. Any help is greatly appreciated.
P.S - Can't use dotnet build, as the solution needs building of licenses.licx files, and the component which builds it (Microsoft.Build.Tasks.LC) is not ported to .Net Core. The suggestion from various posts was to use MsBuild.exe
Our .net core 2.1 solution compiles fine on our local development machines with .net core sdk 2.1.301. Appveyor used to compile the solution in its CI pipeline when there was no database projects defined. Once such a project added, Appveyor started failing in building the solution with the error message below. Any clues how to address this issue?
C:\projects\comingsoon\ComsingSoonDatabase\ComsingSoonDatabase.sqlproj(57,3):
error MSB4019: The imported project "C:\Program
Files\dotnet\sdk\2.1.300\Microsoft\VisualStudio\v11.0\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets"
was not found. Confirm that the path in the declaration is
correct, and that the file exists on disk.
The database project can only be built using the full framework MSBuild tools included in visual studio.
Depending on how you set up appveyor, you need to change your definition to use msbuild.exe instead of dotnet commands.
I'm running MSBuild 4.0 against my .net 4.0 solution and I am getting a lot of error similar to the following:
"E:\Hudson\jobs\HCIM 7.0.0\workspace\7.0.0\HCIM_Dev\BC_HCIM.msbuild" (default target) (1) ->
"E:\Hudson\jobs\HCIM 7.0.0\workspace\7.0.0\HCIM_Dev\BC_HCIM.sln" (Build target) (2:2) ->
"E:\Hudson\jobs\HCIM 7.0.0\workspace\7.0.0\HCIM_Dev\src\Common\HCIM.Distribution.Service\HCIM.Distribution.Service.csproj" (default target) (46:3) ->
(CoreCompile target) ->
DistributionProcessor.cs(6,32): error CS0234: The type or namespace name 'Distribution' does not exist in the namespace 'HCIM.BusinessTransaction' (are you missing an assembly reference?) [E:\Hudson\jobs\HCIM 7.0.0\workspace\7.0.0\HCIM_Dev\src\Common\HCIM.Distribution.Service\HCIM.Distribution.Service.csproj]
When I build this in the IDE, it compiles fine (VS 2015, VS 2013), however on Jenkins and when I locally run my script, these are the errors that comes up.
Looking at the IDE and the .csproj files I see that these assemblies are referenced accordingly.
Thoughts?
This sounds like an msbuild and/or framework version issue. Here's a few things to check:
What framework version are your projects referencing? Maybe one is targeting a higher version than 4.0
Make sure this framework version is installed on build server.
Try adjusting your script to use the same msbuild version as the IDE
Note Msbuild is not part of the framework since VS2013 but a separate download is available for running on your build server.
I wanted to have a look at monodevelop, thinking about possible moving in-house projects written in .Net from Windows to Linux.
I installed mono-complete 4.0.2 and monodevelop 5.9.4 on a clean Ubuntu 14.04 VM, I assume those are the latest/current versions.
Now C# works, but I can't get it to compile any VB code.
Any new VB project I create first refuses to load.
Quickly found (Google) that the mono VB compiler doesn't support framework 4 or higher yet, but the project template generates projects targeted at 4.5.
After I manually edit the project file to target 3.5, 3.0 or 2.0, the projects load (this works for console as well as GTK projects).
But when I try to compile it then, no own code added yet, just the auto-generated base code, it just fails without any error messages.
Build output:
Building: VbHelloConsoleWorld (Debug|x86)
Build started 7/3/2015 10:42:20 AM.
__________________________________________________
Project "/home/luc/projects/VbHelloConsoleWorld/VbHelloConsoleWorld.vbproj" (Build target(s)):
Target PrepareForBuild:
Configuration: Debug Platform: x86
Target GenerateSatelliteAssemblies:
No input files were specified for target GenerateSatelliteAssemblies, skipping.
Done building project "/home/luc/projects/VbHelloConsoleWorld/VbHelloConsoleWorld.vbproj".-- FAILED
Build FAILED.
0 Warning(s)
0 Error(s)
Time Elapsed 00:00:00.0438100
---------------------- Done ----------------------
Build successful.
Am I still missing some dependencies? Other stuff that must be fixed before a VB project will work?
For some reason building VB.NET with MSBuild does not work.
To workaround this you can disable the use of the MSBuild build engine. Go into project options, Build - General and uncheck Use MSBuild build engine. Then the project should compile and generate an output assembly.