I think the classic situations were either 1) mixed language assembly creation, or 2) network deploy of modules that aren't loaded often since modules are demand loaded.
-Brock http://staff.develop.com/ballen > -----Original Message----- > From: Discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of > Shawn Wildermuth > Sent: Tuesday, March 28, 2006 7:56 PM > To: [email protected] > Subject: [ADVANCED-DOTNET] Modules... > > When I got started with .NET after the PDC build some half a > decade or so > ago, I like the idea that an Assembly could contain one more > more modules. > It seemed to me that being able to separate development in a > team across > assemblies that the build could then build into a single > assembly was an > attractive idea. There has never been Visual Studio support for this > (though the command-line compiler for C# does (not positive > about the VB.NET > compiler)). > > Does anyone actually do this in any situations? csc /t:module is > interesting, but I can't find a use where I could recommend > it to a customer > for their production systems. Anyone? > > Thanks, > > Shawn Wildermuth > <blocked::http://adoguy.com/> http://adoguy.com > C# MVP, MCSD.NET, Author and Speaker > > > > =================================== > This list is hosted by DevelopMentor. http://www.develop.com > > View archives and manage your subscription(s) at > http://discuss.develop.com > =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
