Ming mentioned this a while back (June 29th) and unfortunately I didn't notice it until now. I've had a few minutes to play with Yukon (SQL Server 2005 for those way behind in the program) and most of that time was spent hunting for the query diagram tools in the new SQL Server UI. But alas, as Ming stated, it isn't there. To quote from Ming's blog: "Database diagram (it was official cut in VS2005, but who knows, we might be asked to put it back.) -- a diagram to lay out the relationship within the database tables/views/".
Well let the guys know then that they have been official asked. I think Paul Murphy may have said it best in Ming's comments: "Someone should be beaten and flogged for cutting database diagrams from the Yukon/Whidbey toolset.”. I could not agree more.
I could come up with a thousand reasons why this shouldn't have been removed, the least of which being the amount of typing the diagram tool saves me. But they all see so painfully obvious that I can't imagine they were not brought up at meetings inside Microsoft. So this leaves me wondering, did they really have a good reason to remove this (puppies in China will die if they built it for example) or did they just have a collective brain fart when this decision was made?
Or maybe I'm wrong and it is there and Ming never said this and this is all a nightmare and I'll soon wake up and have a beer way to early in the morning in order to toast the dream being over…
Much thanks to Florin Lazar for posting how to fix MSDTC after install SP2 (http://weblogs.asp.net/florinlazar/archive/2004/06/18/159127.aspx). So far this is the only issue I've run into after installing SP2 (knock on wood).
Every have one of those days were it seems like the world is secretly trying to scramble your brains? I'm having one today.For some reason this statement compiles just fine:
if(anyYearCheck.Checked = false && (1 > 2))
}Did you notice the problem? Yeah? Well I didn't.For those like me who didn't catch it, here is the deal; "Checked = false" doesn't check the value of Checked, it sets the value of Checked. So rather than checking for false I was setting it to false. This caused some rather intricate four-letter-word sentences to be expunged by yours truly.What I find odd is that I'm positive that statements like this have cause compiler errors in the past. So like I said, the world must be secretly out to get me.UPDATED: My code sample was wrong. This error requires the && to be included in the if statement.