December 19, 2017 at 6:45 am
I have modified settings inside VS2017 to open .sql files with Explorer.exe. This opens the file in a new tab within SSMS and is the way I've been working for some years now.
My installation of VS2017 seems to 'forget' this setting periodically, following no discernable pattern, so that the .sql files revert to opening in the VS T-SQL editor.
My colleague is experiencing the same behaviour. Has anyone else noticed this?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
January 16, 2018 at 1:53 pm
Phil Parkin - Tuesday, December 19, 2017 6:44 AMI have modified settings inside VS2017 to open .sql files with Explorer.exe. This opens the file in a new tab within SSMS and is the way I've been working for some years now.My installation of VS2017 seems to 'forget' this setting periodically, following no discernable pattern, so that the .sql files revert to opening in the VS T-SQL editor.
My colleague is experiencing the same behaviour. Has anyone else noticed this?
Heh, I guess we're on our own with this one. Still happening & a real wind-up.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply