Do you have code that should be seen by only a subset of members of your on-premises team project collection? Do you use Team Foundation Build (TFBuild)? If so, you must create some custom groups to reduce the risk that unauthorized team project collection members can use a build process to bypass team project permissions.
When you want people on your team to review code in a Git team project on Visual Studio Online, you can use a pull request to review and merge the code. Pull requests enable developers working in topic branches to get feedback on their changes from other developers prior to submitting the code into the master branch.
As Charles announced earlier today, we’ve just released Visual Studio and Team Foundation Server 2013. I’m here today to briefly highlight what’s new in version control and TFBuild and to advise you about a known issue in TFBuild that we’re working to fix.
You want to run some of your business logic during your TFBuild process. Maybe before, or maybe after Team Foundation Build (TFBuild) compiles or tests your code. For example, before you compile, you want to set the version of your assembly files.
I’m here today (and trying real hard to not be jealous of those of you reading this from beautiful San Francisco) to share some new information about version control and Team Foundation Build (TFBuild) in Visual Studio 2013 Preview.
Version control
Git built in to Visual Studio and TFS
Use branches to switch contexts and isolate risk
Resolve conflicts
Work around a few known issues
More of what’s new
Team Foundation Build
Build Windows 8.1 Preview Store apps
Build more simply.
<!–
–><p>By: <a href=”http://social.msdn.microsoft.com/profile/p.%20kelley/”>P. Kelley</a></p><p>On 30 January 2013, we released the first preview version of the Visual Studio Tools for Git downloadable plugin for Visual Studio 2012. We recently became aware of two bugs in this initial preview release that we felt warranted public disclosure.
//
By: Andy Lewis and Matthew Mitrik
Today we’re here to help you:
Specify how you identify yourself on the changes you commit
Specify the default location for Git repositories
Use images (from either TFS or Gravatar) to identify authors of commits
Use a .gitignore file to block clutter from entering your user experience and your repository
Use the .gitattributes file to make sure changes are correctly recognized by the system
Modify Git settings from the command prompt
Got the latest version of Visual Studio with Git?
<!–
–>
//
<!–
Run CI builds in your Git team project
–>
Does your team use continuous integration (CI)? Are you an early adopter of the new Git capabilities in Visual Studio and Team Foundation Service? If so, you’ll be glad to hear that you can define a CI build process that automatically builds and tests the code that your team pushes into your Git team project.
//
<!–
Create, Connect, and Publish using Visual Studio with Git
–>
By: Andy Lewis and Matthew Mitrik (MS)
In the few days since we announced Visual Studio and Team Foundation Service support for Git, it’s been exciting to see so much interest,
By Matthew Mitrik (MS), Andy Lewis, and Martin Woodward
Today we announced the availability of Git for Visual Studio and Team Foundation Service. In this post, we’ll walk through the new experiences.
Get set up: Get the free service, and then you can use it with any Git client tools you want,
