Sahil asks a good question (something I meant to share…thanks for the reminder) about installing the November CTP bits on a machine that already has SQL Server 2005 (Beta 2) on it.

The latest install put SQL 2005 Express on my machine without asking me. I already had SQL 2005 Beta 2 (Oct. CTP) on there. All of my vs.net tests against the SQL Server database continued to function perfectly. However, I cannot open up a connection in the SQL Server Management Studio.It is looking for a method that no longer exists in the Windows.Forms namespace (cool to see that tie to managed code…). Hmm – a few more dialogs I try to open also have similar issues with the

So I’ll probably get the December CTP of SQL Server to see. I’m sure it’s working with something! I clearly missed a piece of information somewhere about that. And I can’t quite answer your question, yet, Sahil. Sorry. 

Posted from BLInk!

Here are some more changes upcoming for the November CTP that I found loading up a project from the October CTP bits:

retyping for Google, etc

System.Transactions.TransactionScope.Consistent is being replaced by Transaction.Scope.Complete

LoadOption.UpdateCurrentValues (used with DataSet/DataTable.Load(dbDataReader)) is changing to the very strange LoadOption.Upsert. Additionally, LoadOption.OverwriteRow is replaced by OverwriteChanges and PreserveCurrentValues is replaced by PreserveChanges.

Lastly, System.Windows.Forms.AutoScaleBaseSize is deprecated. This was automatically created by the Windows form designer as you began dropping controls onto the design surface.

eg:   Me.AutoScaleBaseSize = New System.Drawing.Size(5, 13)

Now, I see these two lines being created instead:

 Me.AutoScaleDimensions = New System.Drawing.SizeF(6.0!, 13.0!)
 Me.AutoScaleMode = System.Windows.Forms.AutoScaleMode.Font

All of this stuff will get helpfully pointed out by VS2005.

Posted from BLInk!