Skip to main content

TechEd 2013 - Day 2

Second day of TechEd 2013 has ended. For me, this day was full off interesting information related to SQL Server and Windows Sever. From my perspective, the most interesting sessions of the day where related to security. During this sessions I realize that we are extremely vulnerable to attaches, even if you change the server password every 4 hours. An attack can be made in 5 seconds – the same problem is on the Linux system, not only Windows.
Things that I consider interesting:

  • Foca – it is an interesting tool to discover what the public content that is listed by an internet endpoint. It will extract meta-information like the name of the users, machines, software version and so on. 
  • It is extremely easy to modify a worm or trojan to make it undetectable and for 100$ you can buy an application that give you the ability to “manage” the infected machine.   
  • You should NEVER have an async method that return void, except when you are working with event handler. If an exception occurs, the exception cannot be catch at the code level. Because of this you will have odd behaviors from time to time like: in Windows Phone this exception will disappear and in Windows 8 this error will cause the application to “die” immediately, without a notifications. Another problem with this kind of calls is when the actions end – because the system cannot tell you when the call end. In this cases you should return Task and not void.
  • If you want to hide the main menu from Visual Studio, that you could try Hide Main extension. Pressing ALT will show the menu back again.
  • When you have Visual Studio open, than ALT + F6 can help you to navigate between Visual Studio windos.
  • Don’t forget SHIFT+ALT will give you the ability to make multi-line editing.
  • If you are using SignalR and you need to create a small cluster and synchronize different servers with SignalR than Windows Azure Service Bus can be a solution for you. You need to write only one line of code to have Service Bus in the backplane.

That’s all for today, see you tomorrow.


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.