-
Notifications
You must be signed in to change notification settings - Fork 224
Can't publish combined project of DNX and 'traditional' class library to Azure #2467
Comments
I'm having the exact same issue. I've created a testing repo to help reproduce it: It's an ASP.NET5 web app referencing a good old class library. When I remove the reference to the library, publishing works just fine. Otherwise i get the error above. @gabrielvdk You can try creating nuget packages out of your old libs as a workaround. |
Hi, Just tried your suggestion by adding a 'normal' NuGet package to the project, same issue. I would build and work fine on my Dev machine, but wouldn't publish to Azure. Here are the publish logs, the first is the failure, the second the succcess. The NuGet package that I used: SD.LLBLGen.Pro.ORMSupportClasses Fail: Success: `Project "ExampleProj.Kitchen.xproj" (MSDeployPublish target(s)):
Done building project "ExampleProj.Kitchen.xproj".` |
I have replicated this using a normal file system publish as well, so it seems like it's not purely an Azure publish. |
It looks like this is caused by a combination of aspnet/Tooling#193 and a real issue in publish. I was able to get a repro of the publish issue in the latest dev code by creating a new xproj and a csproj, adding a reference, restoring the wrapper proj (to work around the tooling issue), and then publishing. Both command-line and VS publish fail with I'll have a fix for the publish issue soon. Until the tooling issue is fixed, you'll have to manually restore the wrapper project (it's in the |
Hi,
I've added my 'traditional' DAL project to an ASP.NET vNext and worked/debugged with it locally without any problems. But when I tried to publish it to Azure it would not. It states '3>Publish failed due to build errors. Check the error list for more details.', but there are 0 in the Error List, also the project runs just fine.
So is it possible to combine 'old' 4.5.1 projects with DNX targetted projects? If so, is Publishing now just an issue at the moment or something else?
As a workaround I tried to create a DNX class library, but that wouldn't allow me (in VS 2015) to add References using the Browse button, so I couldn't port my old class library to the new format as I also require 2 DLL's.
The log of the build
The text was updated successfully, but these errors were encountered: