search

nicholas-ross / SSMS-Schema-Folders

This an extension for SQL Server Management Studio (SSMS). It groups sql objects in Object Explorer (tables, views, etc.) into schema folders.
GNU General Public License v2.0
159 stars 34 forks source link

Extension not working in SSMS 18.5 even after unblocking #15

Open Semanticore opened 4 years ago

Semanticore commented 4 years ago

I previously had this extension running fine on SSMS 17, my company has now sent me a new PC running SSMS 18.5 so I attempted to install it.

I unblocked the zip file, extracted it and placed the folder within the "/Common7/IDE/Extensions" folder as instructed, but when I open SSMS I don't get any warning message and the tables aren't stacked by schema.

I've checked the .dll files and there's no option to unblock them; the only options are "Read Only" and "Hidden".

EddyMJ commented 4 years ago

I unblocked the individual DLLs..still no good. Hoping for a solution.

Note that it the configuration options do appear properly under Tools|Options|SQL Server Object Explorer.

nicholas-ross commented 4 years ago

What is the full file path to the SsmsSchemaFolders.pkgdef file?

If you have extracted the zip to its own folder then you need to go into the SSMS-Schema-Folders-v1.3.1 folder and copy the SSMS Schema Folders folder to the extensions folder. SSMS won't check additional sub folders for the extension file.

All the .dll and .pkgdef files are required. Do not delete any or only copy files that you think will be used.

When you go to Tools > Options > SQL Server Object Explorer > Schema Folders do you see options to change or is it blank?

EddyMJ commented 4 years ago

I've done some more experimenting. It seems that, if there's only one schema, SchemaFolders does not collapse the objects in that schema using SSMS 18.5 (it works as expected using 17.9).

Sorry about the misinformation...I only had the one schema at the time and assumed it just wasn't working. Personally, I find this behaviour acceptable...perhaps even better...so I'd be happy to call this issue closed, but maybe add something to the docs so others don't make the same mistake I did.

Thanx for a great extension.