Skip to main content

Day 3 of TechEd 2012 - Amsterdam

Si s-a terminat si ziua a treia a TechEd 2012. Dupa circa 3 ore petrecute in fiecare zi in Amsterdam RAI, oboseala incepe sa isi faca simtita prezenta. Aceasta a fost ultima zi intreaga. Maine fiind ultima zi, conferinta o sa se termine mult mai devreme.
Astazi am inceput ziua cu sesiunea "Learn Big Data Application Development on Windows Azure". Daca nu ati stiut pana acuma, pe Windows Azure exista si Hadoop, care ne permite sa procesam si sa analizam un volum foarte mare de date.
Dupa aceasta sesiune, mi-a fost dor sa vad putin cod, asa ca m-am dus la "Real World Developer Testing with Visual Studio 2012". A fost o sesiune unde nu s-au prezentat diferite framework-uri pentru a scrie teste. Chiar daca nu tinea de parte de dev, am participat si la sesiunea "Windows 8: BitLocker". S-a discutat despre aceasta noua functionalitate pe Windows 8, care ne permite sa ne luam pe un stick "PC-ul", iar apoi sa il putem rula de pe orice calculator, fara sa ne facem probleme de securitate sau ca putem sa pierdem date.
"Building HTTP Services with ASP.NET Web API" a fost una din sesiunile la care am participat. A fost prezentat Web API de pe ASP.NET destul de detaliat. As fi vrut sa aflu mai multe, dar asta o sa fac cu prima ocazie cand am putin timp liber si o sa sap. Desi a fost o prezentare de nivel 300, din pacate continutul a fost doar de 100.
Ziua de azi s-a sfarsit cu "Creating and Consuming OData Services for Business Applications". In momentul de fata OData Services este extrem de matur si puternic, dar aveti grija Web API vine tare din spate, dar nu o sa fie inlocuit cat de curand de Web API.
Hot tip of the day: In Visua Studio 2012, chiar daca unele functionalitati nu mai sunt asa de usor de accesat, de exemplu sa deschidem Source Control, toate acestea au key shortcuts deja definite.
Cel mai mult am savurat prima sesiune si am fost impresionat de ce putem face cu Hadoop pe Windows Azure. Maine ne luam la revedere de la TechEd 2012 si de la Amsterdam :(


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…