-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Baseclass.Contrib.Nuget.Output 2.3.0 fails on msbuild package #34
Comments
I get this same issue. I've worked around it, the Baseclass.Contrib.Nuget.Output.2.2.0-xbuild02 (was prerelease) version on nuget doesn't have this issue but also resolves the VS2017 error MSB4175: The task factory "CodeTaskFactory" could not be loaded from the assembly issue we had on 2.1.0. |
Thanks for the comments, could you add some additional information:
|
Package is installed using nuget, so packages.config. Solution path is outside of csproj folder like: The package folder is in the root of the solution folder like C:\my-dev-folder\solution\packages\ and hasn't been relocated. |
I am getting this issue as well and I think I have a good idea why. My setup: In order to compile with Visual Studio 2017 I upgraded to Baseclass.Contrib.Nuget.Output 2.3.0. Now things build OK in Visual Studio but it fails in my automated build. My automated build does a web deploy like this:
Note how I am deploying a specific project, not the solution. "Projects" points to a .csproj file, not a .sln file. This appears to be what @gralov is doing also. Turning on diagnostic logging in MsBuild shows that the SolutionDir property is undefined within this MsBuild, I assume because I'm not deploying a solution file. Below is the log file portion for CollectNugetOutputFiles which is what is failing. Note SolutionPath=Undefined. In PackageRetrievalTask that's the SolutionPath property. It's accessed in GetFilteredProjectNugetPackages() when the package source is PackagesConfig. I guess it's trying to get to the actual package that I have stored at the solution level. But since no solution path was passed in, it cannot find it. Kind of makes sense. I'm not sure there's anything you can do about this. I'll try fiddling with my msbuild call to get the solution path passed in. MsBuild Diagnostic Log:
|
Adding the SolutionDir property with the correct value to my msbuild deploy call made things work. |
@gralov @cweb187 @mqtwinter see issue #39 |
@gralov is @mqtwinter resolution ok for you? |
Hi,
I'm having an issue that when trying to package my project for deploy, like msbuild myproject.csproj /T:package /P:Configuration=Debug.
An error ocurre in the Baseclass.Contrib.Nuget.Output.targets file with the error:
The thing is, if I downgrade to 2.1.0 it works. But then VS2017 issue.
The text was updated successfully, but these errors were encountered: