title: can I get .net compiler to do some optimistic caching to speed up the build without refactoring code base into assemblies?
body: <p>my dotnet code base is pretty big (so I don't feel like undertaking refactor into assemblies project) but doesn't change all that much. The build is real slow, although disk speed is fine - apparently it just takes awhile to compile the thing. So IMHO it would have made good sense for the compiler to cache compiled versions of files that haven't changed since last build in the optimistic expectation that no change in another file broke the module. Then if the optimistic assumption proved invalid, the full build could be undertaken. Well, I am pretty sure that things like that are often done while using Java and C++ compilers.</p>
  
  <p>Could something like that be done here in dotnet? If not, why not :-) ?</p>