This is pretty cool, but it reminds me a little of the SQL Query Designer; someone could easily write bad code (even though it may work, it'll have poor performance). I've seen people write SQL code with multiple levels of nested joins and sub-selects this way (most of whom can't write SQL by their self) which took minutes to run. I’ve had to rewrite a lot of SQL like this, and my queries would usually run in less than 2 seconds. I guess any tool could be misused.I hope the Class Designer is much better. I'm looking forward to using this to improve my productivity.I'm really looking forward to all the enhancements coming in Whidbey!
Senkwe Chanda wrote:Are the class diagrams different for C# and VB.Net? That seems to be what was implied, which would be strange to me.
CRPietschmann wrote: This is pretty cool, but it reminds me a little of the SQL Query Designer; someone could easily write bad code (even though it may work, it'll have poor performance). I've seen people write SQL code with multiple levels of nested joins and sub-selects this way (most of whom can't write SQL by their self) which took minutes to run. I’ve had to rewrite a lot of SQL like this, and my queries would usually run in less than 2 seconds. I guess any tool could be misused.I hope the Class Designer is much better. I'm looking forward to using this to improve my productivity.I'm really looking forward to all the enhancements coming in Whidbey!
Where to we are going? Do we really have time to draw useless boxes or we better spend time doing real programming? Are you saying this spaghetti of boxes is more understandable than the source code?
I think it is just a waste of time. Instead of playing with all of those boxes you better spend more time designing application!
Tensor wrote:Dragging and dropping members - when you moved the name field & property to the person class - would you just get the stubs? Or if say I had written validation in my property, would that be copied too? Also, another refactoring question - not sure if this is the place for it! How flexible will the refactoring be? Changing public fields to private and giving them a property is great - is it possible to do custom refactoring which would add in, say a method call in the property set (say, a call to a method which sets a dirty flag)?