Skip to main content

Day 1 of TechEd 2012 - Amsterdam

In aceasta saptamana particip la TechEd Europe. 2012 este primul an cand TechEd se tine in Amsterdam. Locatia aleasa este Amsterdam RAI, un centru de conferinte destul de mare. In unele cazuri iti poate lua si 20 de minunte ca sa ajungi de la o sesiune la alta, iar chiar si cu harta in mana de poti pierde pe holuri.

Haideti sa vedem la ce sesiuni am fost azi. Am inceput cu keynote-ul unde ni s-au prezentat ultimele produse in care Microsoft pompeaza resurse la greu, in special Windows 8 si Azure. Dupa acesta introducere am fost la "Meet the Windows Azure". A fost un overview despre noua versiune de Windows Azure si ce aduce nou. Cel mai importat lucru pentru mine din cadrul acestei sesiuni a fost memory cache-ul, care lipsea pana acuma si modul in care se pot atasa partii virtuale la o masina.
A treia prezentare a fost despre Visual Studio 2012. Mi s-a parut cea ma buna sesiune din ziua de azi la care am participat. De ce? A fost singura sesiune la care am invatat lucuri noi si foarte interesante. Am continuat cu "An Overview of Managing Applications, Services & Virtul Machines in Windows Azure", unde nu am apucat deloc sa ma plictisesc. Am continuat cu Windows Azure, a.i. ultima sesiune pe ziua de azi la care am participat a fost "Cloud-Ready Data Services".
Hot tip of the day: Cei de la Nokia au anuntat ca cea mai mare parte din modele cu Windows  Phone 7 o sa suporte si Windows Phone 8 (seria Lumia si se pare si 610). Asa ca putem sa stam linistiti, strategia lor de marketing ne pune intr-un loc sigur.
A fost o zi extrem de interesanta si imi doresc sa vad asa ceva si in Romania. Ne auzim maine seara.

Update: http://mashable.com/2012/06/20/windows-phone-7-8/ Nokia Lumia 900 with Windows Phone 8. 

Comments

  1. Cei de la HTC nu au zis nimic de upgrade-ul la WP 8? :) (nu WP 7.8)

    ReplyDelete

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…