how understanding churned versions dependencies?


hi i have problem dependency hierarchy i am capricious solve:






the problem i should anxiety dependencies myproject project. i have built baseproject commonutil(version 1.0) built assemblies. myproject i am controlling classes commonutil i am capricious i should anxiety commonutil.v.1.0 i could/should anxiety tide chronicle commonutil (v 2.0).



which commonutils public should i anxiety myproject?
i can't anxiety both assemblies vs tells me can't establish public both enclose same methods. i wholly anxiety v.1.0 i maybe have all i need v.2.0 i wholly anxiety v.2.0 i maybe have capabilities v.1.0 (which baseproject) needs.



Comments

Popular posts from this blog

list macos calm editors formula editors

how hibernate @any-related annotations?

why does floated <input> control floated component slip over too distant right ie7, nonetheless firefox?