Skip to main content

9-10 July, 2015 – Implementing effective web applications with Microsoft web stack

Next month, ITCamp will organize a free workshop about web development with Microsoft Technologies. During the two day workshop we'll talk about ASP.NET MVC, REST API, Angular.JS, Web Security and of course vNext.

More information about this workshop can be found in the fallowing link:
Registration link:

When: 9-10 July, 2015
Where: Cluj-Napoca
Trainer: Andrea Saltarello
Participation fee: 0 (the workshop is free)
Number of available seats: 40 

Target audience: People that are working on web projects with/without a large experience. Before you attended to this workshop, you should have a minimal knowledge about ASP.MVC, EF and Angular.JS. If you are an expert in this technologies or you worked with them on projects for long time, than this workshop would not bring an extra value for you.

Abstract: This two day workshop is dedicated both client side applications (SPA) and also server side (Razor/MVC). For people that already develop web application using this stack it will be a good recap. On top of this we will learn best practices, that can help us to avoid making mistakes during design and developing phase. A short overview related to web security and authentication mechanism will be discussed. At the end of the workshop we will take a look over what Microsoft is preparing to us related to we development. Presents is important, but also the future is. If you didn’t had the opportunity to work with this technologies yes, but you have a base knowledge of web development, that this is the perfect way how you can understand the core concepts of web development using Microsoft technologies.


More information about this workshop can be found in the fallowing link:
Registration link:


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 …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…