Skip to main content

[Post Event] Cloud Conference 2018, Bucharest

Today (April 19th, 2018) I had the great opportunity to be invited as a speaker at "Conferinta de Cloud." I was amazed to find out that around 300 people join this event, that it is dedicated to cloud and Microsoft Azure.
The event has two tracks, one dedicated to the business side and a second one dedicated to technical one. I was surprised to discover that almost half of them were interested in the business track. This is a good indicator that confirms us that cloud is here to stay and Microsoft Azure it is used more and [more in business.

I delivered a session focused on things that we need to take into account at the moment when we start a project on the cloud. People forget to check the most basic things when they kick-off the project. Because of this, they are ending in situations where the consumption is over the limits or data is public accessible.

Session slides can be found below:
Title: Day Zero In A Cloud Project
AbstractIn this session, we will take a look at what we need to keep on our radar when we start a new project inside the cloud. When not only us but also clients are new in cloud ecosystem, we need to be aware of small things that can make a difference or secure the success of the project. Things like security, environment isolation and access controls are just a tiny part of the things that we need be aware. There will be examples from real life projects and hands-on implementations inside Microsoft Azure. After joining this session, you will have an initial view on what things we shall be aware when we start a new project inside the cloud.



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 …

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…

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.