Ayende - It's not necessarily a bad idea. Linux distros have been doing this for over a decade. Upgrade issues are handled by the package management system. Windows and .Net (via Fusion) even has side-by-side installs, and it appears that CoApp is trying to make a package management system which manages upgrades both along the same lines as the existing world of package management as well as using side-by-side versioning.
Honestly, I'd love a package management system which allows me to pull in whatever version of whatever dependencies I need and keeps them separate, as long as I can delegate version binding to my tools/platform. It looks to me that CoApp is trying to do this. -r On Wed, Oct 13, 2010 at 2:50 PM, Ayende Rahien <[email protected]> wrote: > Rory, > That is a VERY bad idea. I am using some app with NH 2.0 and some app with > NH 3.1 > Putting it in the GAC means that I have to install the app in the > destination server. > Better to use XCOPY model > > On Wed, Oct 13, 2010 at 7:24 PM, Rory Plaire <[email protected]> wrote: > >> In regards using a package system in Windows: >> >> There appear to be 2 choices: CoApp and NuPack. CoApp appears to be a >> proper package management system for use platform-wide, and NuPack appears >> to be targeted towards developers finding and getting dependencies. >> >> I'd be more inclined to make a choice towards a system which will allow NH >> to be installed system-wide and then available for use by all .Net apps. >> >> -r >> >> On Wed, Oct 13, 2010 at 3:37 AM, Valeriu Caraulean >> <[email protected]>wrote: >> >>> I agree with idea of NHibernate "package", but only along with a >>> traditional "NHibernate only" one. >>> >>> What do you think about NuPack package management? >>> Will it be practical to have a package with NH, NH Contrib, >>> Fluent/codeconform and what else people uses the most? >>> >>> >
