54

I played with Visual Studio builtin profiling tools and now every time I check out any file this section automatically adds to my solution file:

GlobalSection(Performance) = preSolution
    HasPerformanceSessions = true
EndGlobalSection

I totally removed all profiling reports, then removed local copy of all source control files from this solution and update to latest. This section still in *.sln file after any checkout.

Other teammates who haven't used prfiler doesn't have this problem. Has anyone any ideas?

Jehof
  • 34,674
  • 10
  • 123
  • 155
Denis Agarev
  • 1,531
  • 4
  • 17
  • 34
  • which version of Visual Studio are you using? – Jehof Mar 01 '13 at 08:07
  • 1
    Visual Studio 12. Yes your answer is right I read about it but... it doesn't work for me... maybe I did smt wrong – Denis Agarev Mar 01 '13 at 08:18
  • Are you sure that the Solution file in your source control does not have the GlobalSection entry? Have you checked the file in the Source Control Explorer? – Jehof Mar 01 '13 at 08:23
  • 1
    Related: https://connect.microsoft.com/VisualStudio/feedback/details/817315/section-in-solution-file-causes-continual-merge-conflicts-in-a-team-environment – Eamon Nerbonne Oct 17 '14 at 11:52
  • Actually, it might be helpful if everyone that can reproduce this issue say so on the [connect issue](https://connect.microsoft.com/VisualStudio/feedback/details/817315/section-in-solution-file-causes-continual-merge-conflicts-in-a-team-environment) (there's link next to "Repros" when you're signed in, and/or you could leave a comment). That way, it might get fixed some day - this really looks like a trivial bug. – Eamon Nerbonne Oct 17 '14 at 12:02

2 Answers2

53

Open the PerformanceExplorer in Visual Studio by using the Menu Analyze -> Windows -> PerformanceExplorer and check if it lists any session entries.

If so delete them by doing a right-click on an entry to open the ContextMenu. Then select "Remove" from the menu.

You should also check the folder of your solution if it contains any .vsp or .psess files and delete them. These are the report files of a profiling session.

Jehof
  • 34,674
  • 10
  • 123
  • 155
  • 2
    As if solution files aren't hard enough to merge as they are...The IDE altering the .sln with this means that in most teams of more than 1, if just 1 person has run a profiler (or only 1 hasn't etc), the sln will have a merge conflict every single time...grrrrr – Tim Jarvis Feb 13 '14 at 01:08
  • 24
    In my case Performance Explorer is empty and no `*.vsp` and `*.psess` files are present, but VS still adds these lines to the solution file. Any ideas? – Sergiy Belozorov Feb 26 '14 at 04:37
  • 4
    Connect issue: https://connect.microsoft.com/VisualStudio/feedback/details/817315/section-in-solution-file-causes-continual-merge-conflicts-in-a-team-environment – Eamon Nerbonne Oct 17 '14 at 12:03
  • 16
    In VS 2015, with General settings applied, the "Show Performance Explorer" menu item is under "Debug >> Profiler >> Performance Explorer" – Dave Kidder Aug 03 '16 at 16:04
4

Only way I could solve this was to close the solution, delete *.psess and *.vsp files from the root directory, reset my .sln file to the remote version and reopen the solution. Problem was then gone. This was using Visual Studio 2015 Community Edition.

garryp
  • 5,508
  • 1
  • 29
  • 41