Posts Tagged DENALI

Pass Summit 2011 Announcements : SQLServer Denali Official names

Finally back from Seattle where I was attending the Pass Summit 2011 conference last week.

As always, we have seen some announcements relating to SQL Server made by Microsoft during the key notes, among which a few official namings was revealed :

  • SQL Server codename Denali has now officially become SQL Server 2012 and will be released in the first half of next year.
  • SQL Server codename Crescent will be named Power Viewer
  • SQL Server codename Project Juneau will become SQL Server Data Tools

 

Leave a Comment

[Denali CTP3] No extensibility support, still we can have fun

Today, Mark Pryce-Maher left a comment on my post reporting the lack of support for SSMS extensibility in Denali.

Mark just started a series of posts on how to build extensions for Management Studio in Denali by leveraging the isolated shell it is built on.

Basically, you can build Visual Studio extensions and then targeting the isolated shell of Management Studio, making it a little bit easier to write add ins now than it was in the past.

You can read Mark first post on the topic here.

Update 1 : Mark has published the part 2 of his article here.

 

Leave a Comment

[Denali CTP3] Management Studio : No support for extensibility

So it’s official now, there won’t be support for SSMS extensibility in the next version of SQL server.

It does not mean it will not be technically possible, it is “just” not supported by MS, including no forward/backward compatibility support, no documentation, etc…

Having developed myself several tools to enhance my SSAS experience, I must say that this was on top of my most anticipated feature for years now.

You can find the official info in the BOL here : http://msdn.microsoft.com/en-us/library/ms174219(v=SQL.110).aspx

You can also review the feature suggestion on connect here : https://connect.microsoft.com/SQLServer/feedback/details/265567/ssms-allow-support-for-addins-as-in-visual-studio.

This one was opened back in 2007, I’ve voted for it last year and it was finally classified “Will not be solved” today…

Considering the great expectations a lot of us had for this one, I just didn’t anticipated it would end this way…

Comments (1)