Skip to main content

Visual Studio Online and Team City - How to integrate them

By
Until now I played with Team City and different versions of TFS and GIT that were installed on premises. Today I wanted something more, I decided to connect Visual Studio Online TFS repository to my own Team City instance.
Unfortunately, I discover that even if it is possible, we need to do a special configuration to our Visual Studio Online account for that.
Below, you can find a short tutorial about what you need to do if you want to connect your Visual Studio Online repository to Team City.

 TFS URL
The TFS URL that you need to use is the following, where [accountName] needs to be replaced with you own account name.
https://[accountName].visualstudio.com/DefaultCollection/

ROOT
The TFS path to your repository. In my case the path was following:
$/mssummit2014/CoolWebSite/
This can be obtained very easily from Source Control Explorer windows of Visual Studio.

USERNAME
Surprise. You cannot use by default your LIVE credentials. To be able to connect you will need to use and activate “ALTERNATE AUTHENTICATION CREDENTIALS” from Visual Studio Online portal. To be able to activate them, you need to go login on Visual Studio Online portal, go to your profile and select ‘Credentials’ tab. You’ll need to activate this feature from here, don’t forget to not use the same password as your use for your live account.

Also, I recommend to set a secondary username that can be used to connect to your account. In this way you add a little more protection to your account. The secondary user can be deleted or change is you credentials are hacked.
After you done this configuration, you can set the username with the following format:
##LIVE##\[seccondaryUsername]
Where [seccondaryUsername] is the secondary username that you crated in the portal, few seconds ago.

PASSWORD
The password that you set at previous step.



Done! Enjoy Team City!

Labels:

Comments

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provi...
Post a Comment
Read more