Skip to main content

[Post Event] Global Azure Bootcamp, Cluj-Napoca - 16.04.2016

This was the 4th year when Cluj-Napoca was on map of Global Azure Bootcamp, by ITCamp Community. As usually, the event was focused on hands-on and coding. The number of slides were kept at minimal, at the number of lines of code written during the 5 hours of the event were maximized.

During the event, there were the following 3 workshops:
  • Azure Service Fabric in Action (Radu Vunvulea)
  • Service Bus hands-on (Radu Pascal)
  • Azure SQL Database - Everyone's intelligent cloud database (Silviu Niculiță)
Each workshop length was 90 minutes and it was full with code and samples. In total there were more than 60 people that participate at this event and learned something new about Azure and Microsoft Technologies 

As usually, local IT company offered us the full support to organize this event. A big THANK YOU for our local sponsors that made this events possible (and free):

You can find below my slides from the event. I will add also the other sessions slides, once I receive them.

Azure Service Fabric in Action (Radu Vunvulea)

Code from the workshop:!610321&authkey=!AJzbq2IoILP12_4&ithint=file%2czip

Service Bus hands-on (Radu Pascal)

You can find below a part of the pictures from the event. See you next time!


Popular posts from this blog

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 …

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.

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…