Skip to main content

Winter ITCamp event in Cluj-Napoca, Romania, December 9, 2015

Registration link: itcamp-iarna-2015.eventbrite.com
 În  luna Decembrie, ITCamp (fostul Codecamp) organizează un nou eveniment pentru profesioniștii IT din Cluj-Napoca. Evenimentul urmează să aibă loc pe data de 09 decembrie,la sediul companiei Thomsons - clădirea Olimpia Business Center (strada Dorobantilor, 98-100).
Tema acestui eveniment este "Web Programing - ASP.NET MVC (5)", doua teme sunt pregătite pentru acest eveniment: "What new in ASP.NET MVC, 5 Visual Studio 2015 and Web Tooling" și "Setting up a SPA using Aurelia with Typescript in Visual Studio".
Participarea la eveniment este gratuită. Mulțumim sponsorilor pentru sustinere (Thomsonspentru locație și SDL pentru gustare).
Agendă:
18:00-18:30
Attendee Registration (Cofee Time)

18:30-19:30
What new in ASP.NET MVC, 5 Visual Studio 2015 and Web Tooling
Radu Vunvulea
Do you like challenges? Then the next 60 minutes will be a challenge for all of us. 
We will take a look on the new features of ASP.NET MVC 5, Visual Studio 2015 and Azure WebApp from a web developer perpective (including Web Tooling, Code Maps, Code Lens and vNext). The focus will be on 3 key aspects: Why, Howand When.
19:30-19:45
Coffe Time and Socialization Time

19:45-20:45
Setting up a SPA using Aurelia with Typescript in Visual Studio
Mihai Coroș
In this session I will present how you can get started with developing a Single Page Application using Aurelia with Typescript and ASP.NET 5. We'll build a small application and do some Typescript debugging starting from how to set up the project in Visual Studio 2015 by installing the needed jspm packages and configuring automation tasks with Gulp.
20:45-21:15
Socialization Time

Sponsori:
Thomsons
SDL
Persoana de contact:
Radu Vunvulea - vunvulear#gmail.com
Registration link: itcamp-iarna-2015.eventbrite.com

Comments

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…