File associations

[Frank Kintrup]

First, PL/SQL-Developer is not the actual problem here, the real culprit is Visual Studio
But maybe you can help to mitigate the fallout

We are forced to use Team Foundation Server as source control system and use Visual Studio to check-out/-in files and such.

However, Visual Studio seems to be way to stupid to properly open the registered application for a file extension
Each time I double-click on a accociated file in Visual Studio a new copy of PL/SQL-Developer is launched, even if PL/SQL-Developer is already running. When I double-click the same file in Windows Explorer it is opened in the running instance of PL/SQL-Developer, as it should.

Please add an option that ALL files should be opened in an already running instance of PL/SQL-Developer. If plsqldev.exe is launched with a filename transfer this filename as fast as possible to the running instance and exit (no need to check databases and such).

This way stupid programs like Visual Studio will be usable again

 

[Marco Kalter]

I have added this to the list of enhancement requests.

 

[rbrooker]

if you have plsd associated with .sql files and double click one through windows explorer, you have the same issue too ...