Skip to main content

First impression of Visual Studio Online

2015 started in full force. I’m starting a new project with an interesting setup.
Because of political reasons we decided to go with Visual Studio Online. The initial setup was pretty okay, we configured with success everything we need, from permissions and rights to folder structure and list of tasks.
I was impressed how nice and useful the task board in Visual Studio Online is. Nothings complicate, simple and easy to use. You have the ability to define custom flows, like in the on-premises version of TFS with Scrum and Agile support.
This is the second project where I am  involved where Visual Studio Online it used.

Document Management
The first thing that hit us pretty hard was the integration with a document management system. It seems that there is no full support in this moment to create and integrate a SharePoint web site with
Visual Studio Online.
I expected to be able to create directly from Visual Studio Online a SharePoint web site for my project or to offer another mechanism for document management. Until now there is no integration with Office 365 or other systems.
We could create on an on-premises instance of SharePoint or on Office365 project web site to store and manage the documentation related to project, but we say NO.
Our approach was a base one. On source control we created a folder dedicated for documentation – “Documentation”. Inside it we are adding and manage all the documents that we need.

Team Size
In Visual Studio Online, with a MSDN subscription you can add maximum 5 people in the team to have access to VSO for free. For each additional resource you will need to pay 33.52 per month (remarks: in this price you have the Visual Studio license included).
For all user accounts that are MSDN subscription, the cost is FREE (smile).

Continuous Integration – Automatically build
The build configuration for a project is very simple and strait. It is done in the same way like for TFS on-premises. Nothing special or extraordinary. The base build setup was done in 5 minutes, including unit tests and custom email alerts on build fail.
And now was the time to calculate the costs of automatically builds. In Visual Studio online every month you get 60 minutes free for build. Everything beyond this point needs to be paid. The price per minute is 0.0373e per minute for the first 1200 minutes and 0.0075e per minutes what is beyond 1200 minutes.
Surprise! We calculate how much will costs us to have automatically build on Visual Studio Online…
Build Duration: 20 minutes
Working window on a day: 10 hours
Number of build per day: 30 builds
Number of developers: 4-7 people
Number of days per month: 23 days
Total minutes per month: 13.800 minutes
Minutes cost: 60 minutes free + 1140 minutes at 0.0373e + 12600 minutes at 0.0075e
Cost: 0 + 1140*0.0373+12600*0.0075 
Total Cost: 137.022e
This is the maxim cost of build, because we configured only one build agent. Because of this, even if the build will run more than 20 minutes, the cost should remain the same because we have only one build agent – no builds in parallel.
In this moment I don’t know what to say about the costs. It is low, it is high, it is okay.
In my own opinion, the cost of build is acceptable, because we don’t need to manage the server and if we consume less minutes, then we will pay less. In 6-8 months I will come with come with some statistical data.

Conclusion
Until now the experience with Visual Studio Online was nice, but I keeping my eyes on costs.

Comments

  1. On "political issues" - I think the most difficult problem to overcome is for companies to trust and external hosting company with the source code. However, for startups and personal projects, it might be an alternative.

    ReplyDelete
    Replies
    1. We didn't had any kind of issues. And take into account that we are talking about the client that you work for also (smile). On our case one of our partners preferred VS Online.

      Delete
    2. I know, I was talking in general.. :)

      Delete

Post a Comment

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…