Quantcast
Channel: WE MOVED to github.com/nuget. This site is not monitored!
Viewing all articles
Browse latest Browse all 7612

Created Issue: References in a separate Targets-file breaks add Package [2757]

$
0
0
Hi! I am testing things out and want to move all my common reference to a separate file, we have lots of projects sharing common dlls. This is pure MSBuild so far. Everything works fine, command-line, Visual Studio but not Nuget. The problem when I have moved out the references is that Nuget probably tries to add some that already exist in the common references file. I thought nuget was working off some Visual Studio level integration (as nuget does not work form commandline for managing project dependencies) am I wrong assuming this. Now I get the feeling that there might be some more naive XML parsing for figuring out what dependencies to add to the project-file?

What I have done that Nuget chokes on

1 Moved out lots of common references to a new "References.Target" file
2 This file is then imported from the csproj-file

I have included project file and Target file in a zip




Viewing all articles
Browse latest Browse all 7612

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>