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
Reference NuGet dependencies installed via the #addin directive #787
Comments
Is the intent to recursively descend the dependency tree, or just reference the direct dependencies of the addin? |
Well intent would be to reference anything needed by the addin, so likely yes. Basically equivalent of a nuget install. |
I'll be watching the progress on this one with interest as I haven't quite figured out the best way to do this myself. In Wyam I let NuGet fulfil all of it's requested packages, including transitive dependencies, and then just walk the entire packages collection and add references for every assembly I find. I haven't upgraded to the v3 libraries yet, which I understand are very different, so I'm sure all my code will break when I do. |
@daveaglick V3 is different, nuget core is depreciated and replaced by a number of undocumented assemblies. There's an issue for ET it though NuGet/Home#2243 |
Yeah, I've been stalling and putting it off. "Undocumented assemblies" doesn't sound like my idea of a fun evening of hacking. |
NuGet V3 despite of being "RTM" doesn't feel fully baked. |
@mholo65 this is avail opt in now right? |
@mholo65 so is this a matter of documentation or does something need to be done to close this issue? |
- Fixes cake-build#787 - Don't share project. Only share Gather Cache. - Use DependencyBehavior.Ignore by default. Only set Lowest if load dependencies is set. This way we wont install unneccessary packages and cache gathering is faster.
- Fixes cake-build#787 - Don't share project. Only share Gather Cache. - Use DependencyBehavior.Ignore by default. Only set Lowest if load dependencies is set. This way we wont install unneccessary packages and cache gathering is faster.
So if I'm understanding #1848 correctly, we need to use the in-process nuget client if we want support for installing addon dependencies? |
@nlowe Correct. |
@devlead I enabled the in-process nuget client and added
If this is not the expected behavior I can open a new issue. |
@nlowe, no this is not expected behaviour. Could you raise an issue including minimal steps to reproduce? |
I'm trying to create an addin where you don't have to do anything special to an OOB cake script. Rather than bundling dependencies inside the nupkg, I'd much rather use nuspec dependencies. I see the |
@jnm2 Have you opted for using in proc and load dependencies? As per documented at: |
The problem is that this is an addin. It should work out of the box and without constraining folks' build script setups. |
If opt in sort it now, then it'll work out of the box when we make it default in the future. |
As soon as I add |
Oh no, I just hit a dead end on the other side! It doesn't look like it's possible to include System.Data.SqlClient.dll in the nupkg– it doesn't get copied to build output but rather listed in a .deps.json which I guess I'd have to parse and resolve? Plus it's not really the right solution since another addin may load a conflicting version of the System.Data.SqlClient package. Looks like the only way for this addin to succeed on .NET Core is for Cake to automatically reference its dependencies without requiring the |
When installing a nuget package via the
#addin
directive, the package's dependencies should also be referenced.The text was updated successfully, but these errors were encountered: