Skip to main content

Eveniment: Mobile in the Cloud (13 octombrie - Sibiu, 8 noiembrie - Cluj-Napoca)

iQuest v-a pregătit 2 eveniment extrem de interesante, unde urmează sa țin și eu o prezentare. Sa nu ratați prezentarea lui Bernd Kullick care se anunța extrem de interesanta. Intrarea este libera. Va așteptam pe toți!
Interesat să ții pasul cu cea mai nouă tehnologie și să afli tot ce e nou de la specialiștii cu experiență?
Pe 13 octombrie la Centrul de afaceri Sibiu și pe 8 noiembrie la Hotel City Plaza Cluj-Napoca ai oportunitatea de a participa la evenimentul Mobile in the Cloud, un eveniment marca iQuest cu sprijinul Microsoft. Vei afla cele mai noi informații despre tehnologiile de cloud și mobile development de la profesioniștii care lucrează la probabil cel mai mare proiect de Cloud din Europa.
Programul pe care ți-l propunem este:
9.00 – 9.30 – Registration & Welcome coffee
9.30 – 9.45 – Keynote
9.45 – 10.15 – Introduction in Microsoft Windows Azure cloud platform, Zoli Herczeg, Evangelist, Microsoft
10.15 – 10.45 – Azure project showcase: EyeOnEarth, Bernd Kullick, Senior Consultant – Windows® Azure, Microsoft Services Germany
10.45 – 11.00 – Coffee break
11.00 – 11.30 – Development of cloud connected Smartphone Applications, Petru Jucovschi, Evangelist, Microsoft
11.30 – 12.30 – Sudoku7: A Windows Phone 7 and Azure Development Experience, Radu Vunvulea, iQuest
12.30 – lunch
La Sibiu, evenimentul se va desfasura in sala de conferinta din corpul A, etajul 2, al cladirii Centrul de Afaceri Sibiu, iar la Cluj-Napoca, locatia este sala Ballroom a hotelului City Plaza Cluj. Detalii suplimentare si update-uri se gasesc pe pagina dedicata evenimentului .
Participarea este LIBERĂ, în limita locurilor disponibile – rezervați-vă chiar acum unul pentru Mobile in the Cloud!
Ne vedem acolo!


  1. Ne-am vazut, si a fost ok. Bafta in continuare in Cluj, fara emotii ca e foarte bine ce ai facut.


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