Compiling and building in .NET results in DLLs, not loose bytecode or IL. When your project gets large, it can take a significant amount of time to build all the dependencies. You really see this when doing a lot of NUnit testing. I like to go back and forth between code and NUnit (using test-first programming), and it becomes a real pain when you have pauses all the time for building DLLs because of one change. Our .NET solution is composed of 16 projects, so a change to the domain layer project can cause the building of many other DLLs. I now appreciate the incrementalness of Java with loose .class files or with Smalltalk with the image file. Yeah, the C# compiler is blazingly fast, but it does take time to build DLLs. .NET programming yields a much different development experience when compared to Java.
powered by performancing firefox