Hi Ian, > I think a rebuild's going to be necessary.
I started with this as a real possibility and have come full circle to accept it as .NET reality since the build process for multi-file assemblies is likely to be alien to most .NET devs. <SNIP> > In short, while in Java, the 'compile' and 'package' steps > are separate, in .NET they form a single step. Concise. Precise. <SNIP> > (As an implementation detail, there's nothing stopping a > compiler performing some kind of optimization here. For > example, your compiler could compile each individual source > file into per-source-file binary files that it stores as part > of its build output. So it wouldn't actually need to > recompile everything. So whether or not the recompilation > really happens depends on the compiler. But that's just the > implementation detail - all that really matters is: does the > build take too long?..) Nope. It's not a build-takes-too-long issue. It's more a build-flexibility and process/tool-support issue. As in:- If my extensible framework required all plug-ins to be multi-file assemblies, would that hurt it's acceptance given that VS.NET doesn't [AFAICT] support building such assemblies. I'm thinking it might... Kunle =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
