Skip to main content

[Post Event] ISTA Conference 2015, November 18-19, Sofia Bulgaria

This week I had the great opportunity to be one of the speakers of ISTA Conference. This was the 5th edition of ISTA Conference and it seems that every year ISTA Conference becomes not only bigger and bigger but also the quality of the session is higher and higher.
This year there were more than 30 speakers from 3 different continents, 2 keynotes, more than 26 sessions, 4 tracks in parallel and a full day of workshops. On top of this all tickets were sold out. Great job!

From my point of view, it was one of the best organized conferences. All the events went very smoothly, all the time internet connection was working, you were able to find enough water and coffee and during the lunch break there was enough food for everyone. This small thing makes a big difference. On top of this, the local speakers presented all their sessions in English, in the end all speakers were able to join and understand all the sessions.

At this conference I talked about cloud and how we should design a system that can scale over the boundary of a cloud provider. You know, even if you are using cloud, this doesn’t mean that you have no limitations. Each service has his own limits and you need to know how to handle the situations when this limits are hit.
Below you can find the slides from my session.

See you next year.


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 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)

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

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…