Skip to main content

Visual Studio Online and Team City - How to integrate them

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!

Comments

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

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

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.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…