Today I upgarded my ssms version to 7.15. And now unable to script objects (F2).

Error:
Object reference not set to an instance of an object

Same issue here.

Me too...

same here!

Same here upon upgrade to SSMS 17.5

Same issue also, also right after upgrade to SSMS 17.5 too.

Running latest version of SSMSBoost: 3.2.6578.26291, build date 04/01/2018, Community licence

Same problem after upgrade to ssms 17.5. Installation of 17.4 and ssmsboost reinstallation didn't help

Same issue!

Hi, I also had this problem and seeing as there is no response from staff I thought I should just inform everyone that downgrading to 17.4 (uninstalling Management studio and using the "install" client, not the upgrade from another version) solved this problem for me.

Solutions Crew, please fix this. It is by far the most used feature for me (at least the most time saving).

You can find the older versions of SQL server management studio here:
https://docs.microsoft.c...s#previous-ssms-releases 

This has been going on for a month or more now with no response from the SSMSBoost team much less an actual fix. I feel sorry for those who have paid licenses - $150 a pop to get no fixes would be pretty frustrating!

Same issue in 17.6

I'd say the issue is not so much that there's a bug but the fact that SSMS is now updated regularly but ssmsboost does not seem to handle compability. I won't be renewing my license if they can't solve that problem.

Dear users, we are working on the release with the fix for v17.5 support. Microsoft has changed several interfaces and parts of the code had to be revised and rewritten. SSMS is evolving, and we have no influence on decisions, made my Microsoft team. Currently we have to support up to 5 versions of source code for some of the features, to ensure compatibility through all versions of SSMS since 2008R2. Effort, required to support new modifications in SSMS architecture spread from several hours to several weeks or even months.
SSMS 17.5 appeared when we were in the middle of the implementation of the next release and we could not make a “small update” anymore. We have decided to complete at least features in progress and the release the fix with them. We will be releasing the beta of SSMSBoost v3.3, with fixed SSMS 17.5 compatibility by the end of the weekend. On Monday, 26.03 you will be able to use SSMS 17.5 with Beta of SSMSBoost 3.3.

I am also sorry for delayed communication. Sometimes we do not know, how log the fix can take. Now it is clear and we are practically preparing the installations of the beta release.

http://www.ssmsboost.com...3842-SSMSBoost-v3-3-Beta 

Thanks!
Tested "go to definition(f2)" functionality using ssms 17.6 - no problems