When rebuilding the solution, the .sln file is checked out and following section is removed:
GlobalSection(Performance) = preSolution
HasPerformanceSessions = true
EndGlobalSection
Why is it happening and how can I prevent checking out solution file on rebuild?
Using Visual Studio 2015 Update 1 and TFS 2015
Rebuild the solution will not check out the file in source control by default.
The delete action trigger the check out. Because version of the Solution file not sync each other from source control and local project folder.
So, the real problem is why rebuild the .sln file will remove the GlobalSection(Performance) file.
This seems to be caused by the Visual Studio issue, refer to following links for details:
Section in solution file causes continual merge conflicts in a team environment
Visual Studio Performance Explorer adds user-specific information to the .sln file, which causes issues for teams with multiple developers
Related
I upgraded a visual studio 2012 web form application to Visual Studio 2012 and added the upgrade to tfs 2010. As part of this upgrade process, I removed a web deploy project from the solution file since I do not need the web deploy 2010 project anything. The application is now being deployed as a publish website.
The problem is When I obtain the updated solution file from TFS, it keeps saying 'projects have been recently added to this solution. Do you want to get them from source control? If I click yes, it wants to open -Deploy.wdproj that is not supported by the application.
If I click yes, nothing else happens. Should I get rid of this message?
According to your description and error message, this seems due to the project that was deleted from source control but still referenced in the .sln. The .sln was not aware of this. Please checkout the .sln file, and update the reference.
Another solution is unbinding and binding again the solution file.
1. Unbinding the solution file from TFS
Unbind the solution file (.sln) from TFS. Go to the menu File =>
Source Control => Change Source Control.
2. Cleaning the solution file by deleting globalsection
Clean the solution file (.sln) by opening it in a text editor. Remove
all occurences of GlobalSection(TeamFoundationVersionControl) =
preSolution. Including the mentioned starting tag and the ending tag
EndGlobalSection.
3. Bind the solution file to TFS again
Finally bind the solution file (.sln) to TFS again. Do this in visual
studio by going to the menu`File => Source Control => Change Source
Control
Take a look at this similar question: Every time I open my VS solution I get “Projects have recently been added to this solution. Do you want to get them from source control?” Hope this helps.
I usually get this problem with my visual studio TFS.
When I add a new item (*.cs, *.js...), it does not add to the source control automatically. But the *.csproj file does include the file.
I am sure that I did not change any related settings.
I solved it by modifying the local config file LocalItemExclusions.config, because there is *.lib in my solution's name, it will be excluded.
When I deleted this line <Exclusion>*.lib</Exclusion> in the config file,
it worked (or you can change the namestyle to avoid it).
Double check if there are folders and branches called Release in your soucre control and their contents is automatically excluded from TFS (along with Debug and lots of file types). You can override this for particular folders by creating a .tfignore file.
More details about the solution please refer this similar question: Visual Studio 2015 new files not being added to source control automatically
If above is not working, check if you source control binding is correctly. File > Source Control > Advanced > Change Source Control.
If not, bind the solution and project to your source control server (unbind first if it's already bound).
I'm using Visual Studio 2015 update 3 with TFS hosted at visualstudio.com.
When I add a C# class file to one of my projects in Visual Studio, it's not automatically added to source control. For other projects in the same solution, C# class files are added automatically, as expected.
When I then add the file, manually, in the project with this problem, I get the following question;
I have to confirm to add the file to source control.
There is a similar question (Visual Studio 2015 new files not being added to source control automatically), associated with a "release" branch, which is not the case here (at least I think so - our TFS-project has never been branched)
We've never configured any .tfignore manually.
This started to happen recently and occurs on all development machines, so it's probably not a client machine issue.
I'm clueless, so any help is highly appreciated.
UPDATE
I've discovered that the problem occurs in projects with names ending with ".Lib"
Projects:
Core (ok)
Core.Lib (files not added automatically)
Communication (Ok)
Communication.Lib (files not added automatically)
I tried to add a test project Test.Lib to my solution. This project was not added to TFS either, but project Test was.
The "lib" extension is the problem. Try renaming the project folder to something else, eg. "CoreLib".
To reproduce this behavior / bug, try the following:
Create a Test directory in a directory controlled by TFS
Create a Test.Lib subdirectory in this directory.
Add a file, test.cs, to Test.Lib. (Test\Test.Lib\test.cs)
In Visual Studio's Source Control Explorer, try adding the new Test directory to source control. You'll see test.cs on the "Excluded items" tab.
The "lib" extension is used by binary files, and these are ignored by Team Explorer by default. I haven't found an official list of filetypes anywhere, but other affected file types are dll, exe, obj and possibly others. You can include these files manually by right-clicking them and selecting "Include".
Got a bit of a weird problem. I'm checking a solution out of TFS source control, and not making any changes to it; just opening it using the SLN file. If I then close Visual Studio (or do a Save All), Visual Studio prompts me to save the SLN file. Even if I do (by overwriting it, it's a read-only file), it continues to do this every time I open and close the solution, as if I'd added a project or something. Why would Visual Studio do this? What's causing it to think the solution has changed and needs saving?
OK, problem solved. As we're using TFS for source control, you're meant to check in the SLN file's corresponding .vssscc file. As we'd checked in the .vspscc for the various projects the SLN file pointed to but not the SLN's .vssscc file, Visual studio didn't consider the solution to be bound. :-)
Fixed it by going to File | Source Control | Change Source Control, then binding the SLN file to the solution's root dir on the TFS server. This created the solution's .vssscc file, which we've checked into source control. Subsequent checkouts now don't cause the problem.
I would start by letting it save the solution and then doing a visual diff of the version that it saved vs the one held in source control to see what the problem is. It could just be white space formatting. Also, are you the only person suffering this (if others are using the same solution?)
I created a C# project and added it to source control (mercurial). I can edit files in VS, commit it and push it using TortoiseHg. It goes to the server. When some one pulls they get the files.
In my visual studio I added a folder and a file inside that folder. I used TortoiseHg and it saw the new file in the new folder. I committed it and pushed it.
However, now someone pulled the latest code from the server - and they got the new file (it is visible through windows explorer), but when they open the solution in VS, they don't see the file.
Does someone have an idea what is wrong here? or things I should check? Thank you for the help.
P.S. I have visual studio 2010 express (so I can't use the VisualHg plugin).
Visual Studio caches changes to the solution and project until an explicit save or a build. In your comment:
In my visual studio I added a folder and a file inside that folder. I used TortoiseHg and it saw the new file in the new folder. I committed it and pushed it.
I see that an updated .sln or .vcproj file was not mentioned and checked in. Did you see an update to either of these files via TortoiseHg? If not, make sure to build or save your project after a change like this.
Did you make sure that the Visual Studio Project File or Solution file is being updated and committed?
VS solution contains projects and each project select managed files by metadata(***.vcproj file). It's not the way include all files from root directory.
So, your co-workers can see new added files by in following two ways.
1) share project file(***.vcproj)
2) manually add files in each person's VS instance.