How did I miss this until now?
http://research.microsoft.com/en-us/projects/Pex/
http://social.msdn.microsoft.com/Forums/en-US/pex/threads/
http://www.codeplex.com/Pex/Wiki/View.aspx?title=MbUnit%20Extension&referringTitle=Home
http://blog.benhall.me.uk/2008/08/how-to-have-pex-generate-nunit-mbunit.html
Technorati Tags: C#, Compilation tax, Coding Horror, Visual Studio I've been watching this with interest Coding Horror: C# and the Compilation TaxDennis Forbes - Pragmatic Software Development : Process, People, ProgrammingCoding Horror: Background Compilation and Background Spell CheckingKnowing.NET - Death and Taxes: Compilation, Type, and Test My opinion is quite simple. Give people what they want. If not they will implement it themselves. I use a workaround. I have three build commands. I've just changed some code, and I am not 100% certain it will compile so I want a quick answer. I use F6 redefined to Build.BuildSelection. This builds just the current project and its dependencies. It doesn't require me to press No because it doesn't ask me if I want to run the last good result. It just lets me see how many errors and start fixing them with Ctrl-Shift-F12. Its the fastest way I know to compile just what I have changed. I've got an assembly building. Now I press either, Repeat Test Run from TestDriven.net (Jamie, Can we have a keyboard shortcut please.)or F5.Either of these will now build just the application I need to run/test, and will detect that I have already built some of the dependencies so it doesn't spend time rebuilding what it already has. Finally its Ctrl-Shift-B. This is the checkin build. Build everything. Run all your unit tests, and finally checkin. It gets me closer to an ideal. I am completely with Larry O'Brien on what I really want, but I am not going to get it until the next version of Studio, unless somebody comes up with a better IDE.
For a while now I've been developing an application to help out at work. Most professionals whatever there profession will have a notebook on their desk which gets filled up with task lists, meeting notes, and jotted down ideas. My problem is that as I review my notebook, its just packed with attempts to visualise either an object model (classes) or object graph (instances) so that I can explain an issue with a co-worker.That's where CodeStruct started. I just wanted to be easily show things likeThis is a class and it's supposed to work in a UI, business object or data tier. That the system is composed of these different applications. Windows Clients, Web Sites, Web services and they hang together like this. This assembly is used in all these applications (which make up a system), but it actually contains classes which are only ever used in one of them.As you can see it's a system visualisation tool that goes way beyond the current Class Designer that's built into Visual Studio 2005. Here's an example diagram showing the Assembly tree of the application and the initial Class designer functionality.How did it get all that information? By reading the dll's of course. There's no point in having a diagramming tool that can't read in the existing information. There's already Visio for that.The other thing is the layout. Its all automatic. Sizing, arrows, positioning; All automatic. I'm think I'll need to different strategies at different levels in the diagram, including one which allows manual control. Fortunately the diagramming engine was built with that in mind.TagsCodeStruct, C#, Diagramming Tool