visual studio - Shortcutting NuGet locally -

we have 2 visual studio solutions, f , c. f framework. c client uses dll:s produced f.

we don't want create single solution containing both f , c. rather, want f produce nuget package consumed c.

our current solution manually run script copies dll:s produced f specific folder in c. copied dll:s referenced files c. binary dll files checked in version control. not elegant, fast. copy takes fraction of second.

our experience nuget becomes hindrance when doing development locally of both f , c. let's developer doing work on interface of f , how c uses it. developer has work in both f , c, switching , forth frequently.

in scenario copying dll:s each time f updated fast. if introduce nuget, process considerably slowed down:

each time f modified needs built on teamcity produce proper nuget package. c must nuget update on projects using nuget package new version. both waiting teamcity build , updating references slow. first takes mintues, second can take in order of minute.

alternatively, f compiled locally produce nuget local nuget repository. faster teamcity build. nuget references in c still need updated, still slow. , package.config of c contain reference nuget version not exist on central nuget repository, error prone. also, have configure c read local repository, should not checked in. local repository has cleaned when done local devolopment.

what better if circumvent nuget locally, did not have update nuget references @ every change in f. there smart way of doing this? our scenario seems standard requirement me. i've seen problem in 2 major projects now.

we've tried use reference paths in visual studio, hoping override path binaries way (and still use copy script bring on dll:s separate folder). hintpath seems take precedence on reference path.