tag:help.appveyor.com,2012-11-13:/discussions/problems/5232-need-to-build-aspnet-core-project-using-devenvexeAppVeyor: Discussion 2018-10-19T08:18:00Ztag:help.appveyor.com,2012-11-13:Comment/406675372016-09-18T03:50:04Z2016-09-18T03:50:04ZNeed to build Asp.Net Core project using devenv.exe<div><p>We've added <code>Visual Studio 2015 - GCE</code> build worker
image under your account. It allows running builds on GCE where the
latest updates are already available. You can specify it in
appveyor.yml as <code>image: Visual Studio 2015 - GCE</code>. Note
that it takes 3-4 minutes to provision a new VM instance and start
the build.</p>
<p>When the update is rolled out to Hyper-V environment you will be
able to run on default build worker image.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/406675372016-09-18T09:29:58Z2016-10-05T12:20:44ZNeed to build Asp.Net Core project using devenv.exe<div><p>Hmm, I added <code>image: Visual Studio 2015 - GCE</code> to our
yml and I'm guessing it used the correct image it took several
minutes to provision instead of seconds. However the build still
failed with:</p>
<pre>
<code>14> Compiling <project> for .NETFramework,Version=v4.5.2
14>C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\DotNet\Microsoft.DotNet.Common.Targets(262,5): error : Object reference not set to an instance of an object.
14> C:\Program Files\dotnet\dotnet.exe compile-csc @<projectpath>\obj\Release\net452\dotnet-compile.rsp returned Exit Code 1
14> Compilation failed.
14> 0 Warning(s)
14> 0 Error(s)</code>
</pre>
<p>Any thoughts?</p></div>leecheneler1tag:help.appveyor.com,2012-11-13:Comment/406675372016-09-18T15:32:38Z2016-09-18T15:32:38ZNeed to build Asp.Net Core project using devenv.exe<div><p>We've been testing with that sample project you provided and it
worked: <a href="https://ci.appveyor.com/project/appveyor-tests/mixed-net-core-solution/build/1.0.2">
https://ci.appveyor.com/project/appveyor-tests/mixed-net-core-solut...</a></p>
<p>Do you use appveyor.yml for configuring the project? Image
should be specified there if so, not on UI.</p>
<p>Also, try RDPing into build worker and see if it works there
while running from command line or IDE: <a href="https://www.appveyor.com/docs/how-to/rdp-to-build-worker/">https://www.appveyor.com/docs/how-to/rdp-to-build-worker/</a></p>
<p>-Feodor Fitsner, AppVeyor</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/406675372016-09-18T16:08:28Z2016-09-18T16:08:28ZNeed to build Asp.Net Core project using devenv.exe<div><p>The interesting part is that you are getting <code>0 warning(s),
0 error(s)</code> yet the build fails. Compare to the build results
of your sample app on the current image: <a href="https://ci.appveyor.com/project/appveyor-tests/mixed-net-core-solution/build/1.0.4">
https://ci.appveyor.com/project/appveyor-tests/mixed-net-core-solut...</a></p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/406675372016-09-18T17:22:18Z2016-10-05T12:20:44ZNeed to build Asp.Net Core project using devenv.exe<div><p>Yes it is odd...</p>
<p>I created an issue on the aspnet tooling repo in GitHub ages ago
but they haven't responded yet :/</p>
<p>So the work around no longer works?</p>
<p>I'm just about to rdp onto a build</p></div>leecheneler1tag:help.appveyor.com,2012-11-13:Comment/406675372016-09-18T17:24:43Z2016-09-18T17:24:43ZNeed to build Asp.Net Core project using devenv.exe<div><p>You mean workaround of creating an empty app in IDE? It works,
but for this "test" repository you provided. I guess somethings is
different in your main "bigger" app.</p>
<p>Look around via RDP - maybe you'll spot something unusual.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/406675372016-09-18T17:28:42Z2016-10-05T12:20:44ZNeed to build Asp.Net Core project using devenv.exe<div><p>Yeah hopefully something will stick out... Its strange though,
fundamentally our app is no different, just contains 20 or 30
projects in the solution, and one happens to be aspnetcore and
reference a couple of full dotnet projects.</p>
<p>If can't get it to work I'll have to have the dependant
libraries build to a single folder on debug and release and
reference the dlls explicitly in a relevant path... never done it
with core but you must be able to!</p>
<p>Pah, hopefully they sort this out before the tooling comes out
of preview :P</p></div>leecheneler1tag:help.appveyor.com,2012-11-13:Comment/406675372016-10-13T03:12:32Z2016-11-30T07:50:09ZNeed to build Asp.Net Core project using devenv.exe<div><p>Hi Guys,</p>
<p>I was experiencing the same issue with my 'ASP.NET Core Web
Application (.NET Framework)' solution. I was able to fix it after
changing my 'appveyor.yml' file like shown below:</p>
<p>From:</p>
<p>before_build:<br>
- nuget restore .\AnnetKatan.sln</p>
<p>To:</p>
<p>before_build:<br>
- dotnet restore</p></div>oleg.burovtag:help.appveyor.com,2012-11-13:Comment/406675372016-10-19T06:14:17Z2016-10-19T06:14:17ZNeed to build Asp.Net Core project using devenv.exe<div><blockquote>
<p>Msbuild doesn't support building Asp.Net Core projects</p>
</blockquote>
<p>It should; you just need to call msbuild on the sln file. I'm
doing this for ReactJS.NET and it's working fine: <a href="https://ci.appveyor.com/project/Daniel15/react-net/build/168">https://ci.appveyor.com/project/Daniel15/react-net/build/168</a></p></div>Daniel15