Bug: Automatically group doesn't work for Visual Studio 2017

I have Groupy set to automatically group for Visual Studio 2017 (devenv.exe) but it does not work. It does work for other apps such as File Explorer and Word, but not Visual Studio.

Let me know if you need any other information.

groupy

Advanced Search

Watch this post

Do not email me updates for this post Email me updates for this post

Successfully updated karma reason!

I should mention that it appears to be working now. I have NOT installed a new version, so I'm not sure why it wasn't working at first, but it appears to be working now.

Successfully updated karma reason!

It does not work. Steps to reproduce:

1. Create auto group for VS 2017

2. Start VS 2017 via desktop / start menu icon

3. Double click on an SLN project file in windows explorer

The important step is that one VS instance is started via shortcut and the other is started by opening a visual studio project file from windows explorer. Then the grouping will fail.

Successfully updated karma reason!

Neil Banfield

Join Date 04/2001

+1104

Quoting dgsdhgsdhsh,

reply 2

It does not work. Steps to reproduce:

1. Create auto group for VS 2017

2. Start VS 2017 via desktop / start menu icon

3. Double click on an SLN project file in windows explorer

The important step is that one VS instance is started via shortcut and the other is started by opening a visual studio project file from windows explorer. Then the grouping will fail.

Are they both opening the same version of Visual Studio? What does Taskmanager show for the path for each?

The installed path is considered for grouping so two installations of VS would not group together automatically.

Successfully updated karma reason!

Sign Up or Login and this ad disappears!
There are many great features available to you once you register. Sign Up for a free account and browse the forums without ads.

Yes they have the same path according process explorer but they are not grouped:

I don't know how exactly your grouping works but I would guess the VS started from a project file in windows explorer works different than starting VS from shortcut. And I would assume the OP has experienced the same problem so perhaps you are able to reproduce and analyze it.

Successfully updated karma reason!

Neil Banfield

Join Date 04/2001

+1104

Are your VS instances elevated or running as normal?

Successfully updated karma reason!

They should run normal, there was no UAC prompt (unless Microsoft suppress this when VS is launched from taskbar which I doubt) and I didn't launched them evelated myself..

Have you actually tried to reproduce this? There is 30 days trial for VS, I gave you a step by step. I think if you would take a look on it yourself its better than waiting for me to reply as you can get all desired information yourself.

Successfully updated karma reason!