Comments
Sort by recent activity
Hi;
The ecosystem project is active - in the sense that the downloads are still available and it's possible to build addins against it - but we wouldn't recommend people start new addins using it, as it not possible for us to support the latest version of Management Studio with the framework.
In the latest preview builds of Management Studio, Microsoft have switched the shell from VS2010 to VS2015, and in the process have disabled the old addin mechanism, meaning all future Management Studio extensibility will be done through .vsix packages, as with Visual Studio. These packages require up-front (build-time) declaration of buttons, commands and menu entries required by extensions, which means that it is no longer possible for the framework to dyamically load plugins and create interfaces for them - which is the main benefit provided by the Ecosystem Project.
Existing addins on will continue to work on SSMS2014 and earlier, and the ecosystem framework will continue to work for that, but for anything newer, you will have to build a .vsix package.
Regards;
Chris / comments
Hi;
The ecosystem project is active - in the sense that the downloads are still available and it's possible to build addins against it - but we wouldn't recommend people start new addins using it, ...
I've had a look at this and I think I've identified the cause of the problem. I should have a fix very soon and will post here when it is available.
Chris / comments
I've had a look at this and I think I've identified the cause of the problem. I should have a fix very soon and will post here when it is available.
Chris
Hi;
Just a quick update on this: we have a fix which we hope to roll out on Monday (18th April), barring any other problems.
Chris / comments
Hi;
Just a quick update on this: we have a fix which we hope to roll out on Monday (18th April), barring any other problems.
Chris
Hi krm;
Unfortunately, it is not technically possible to bring SIPFramework support to SSMS2016. In changing to the VS2015 shell for SSMS, Microsoft have switched from the old addin format to the new .vsix extension format as used by Visual Studio; one side effect of this change is that integration points such as buttons, commands, toolbars and menu entries have to be statically declared up-front. As it is not possible to dynamically create these, SIPFramework cannot function as it currently does in pre-2016 versions of SSMS.
We are still working on a strategy for supporting developers using SIPFramework to build their addins for SSMS2016 - we have an internal technical solution to make migration to the new extension format more straightforward, but as the sands are still shifting at Microsoft's end, we don't want to commit to anything until we know exactly where we stand - for example, if Microsoft decide to build an SSMS extension gallery similar to the existing Visual Studio gallery, we would probably encourage people to move to that.
Regards;
Chris / comments
Hi krm;
Unfortunately, it is not technically possible to bring SIPFramework support to SSMS2016. In changing to the VS2015 shell for SSMS, Microsoft have switched from the old addin format to the n...
There is now an updated version of this beta (2.3.0.275) available. The changes are internal but should help interoperability with future SSMS releases and other Redgate products.
You should uninstall the previous beta before installing this version. Download here / comments
There is now an updated version of this beta (2.3.0.275) available. The changes are internal but should help interoperability with future SSMS releases and other Redgate products.
You should uninst...
Hi;
There are no plans at the moment for a Visual Studio version of SQL Search; however, it doesn't feel like it should be too hard to get a version running, given the fact the new SSMS is built on the VS2015 shell. If other people are interested in this, please let us know and I'll add it to our backlog for consideration.
Regards;
Chris / comments
Hi;
There are no plans at the moment for a Visual Studio version of SQL Search; however, it doesn't feel like it should be too hard to get a version running, given the fact the new SSMS is built on...
There is now also a beta of SQL Search 2.3 also including support for SSMS March 2016 Preview Refresh, which you can download from the forum post here. / comments
There is now also a beta of SQL Search 2.3 also including support for SSMS March 2016 Preview Refresh, which you can download from the forum post here.
Hi;
I'm sorry you're seeing this problem - it's not something we've seen internally, so I've filed a bug report (SDI-687) indicating that under some circumstances it appears to consume more memory than expected and crash out Management Studio.
As we've not seen this happen internally it would help if we had a little more detail to narrow down what we're looking for - in particular, do the databases you are searching contain a very large number of objects, or any programmable objects (stored procedures, functions, etc) with an unusually large amount of code in them?
Regards
Chris / comments
Hi;
I'm sorry you're seeing this problem - it's not something we've seen internally, so I've filed a bug report (SDI-687) indicating that under some circumstances it appears to consume more memory ...
Hi;
My apologies about that - the release notes didn't get uploaded with the 2.2 release; I'll get that sorted out.
The main things are:
* Support for SQL Server Management Studio 2016 CTP3
* Support for connecting to and searching Azure SQL Databases
* Auto-complete in the search text box
* Respects the RGTEMP environment variable - set this to change where the index caches and log files get stored
* Some minor stability fixes
Installed versions will update automatically to 2.2, but to use SQL Search in Management Studio 2016 CTP3 you will need to download the full installer from the website.
Thanks;
Chris / comments
Hi;
My apologies about that - the release notes didn't get uploaded with the 2.2 release; I'll get that sorted out.
The main things are:
* Support for SQL Server Management Studio 2016 CTP3
* Suppo...
Just to update you all on this issue: I've taken a look at this issue and believe I have a fix for it. We still need to do a bit more testing, but hopefully we should be able to push the fix live sooner rather than later.
Regards; Chris / comments
Just to update you all on this issue: I've taken a look at this issue and believe I have a fix for it. We still need to do a bit more testing, but hopefully we should be able to push the fix live s...