Skip to main content

TechEd 2013 - Day 4

Last day of TechEd 2013 ended, goodbye Spain. This day ended with a lot of interesting sessions related to Windows 8, Azure and Big data. I discover new ways how we can use Bitlocker for enterprise customers and why different 3rd party prefer to use Bitlocker and give up of their own mechanism.
I think that you heard that the preview version of Windows 8.1 can be downloaded from Microsoft news. Be aware, if you install the preview version of Windows 8.1, moving to the final version of 8.1 will not be so easily. When you go to the preview version, don’t let the installer to update the backup partition also. In this way it will be very easily to go back to 8.0 and install the final version of Windows 8.1. In general I prefer to use install the preview version of any software o virtual machines.
While attending to a session about big data and Hadoop I find out how you can increase the performance of a reduce operation. During the reduce operation it is recommended to have as few as possible. Even if the size of the files is big, it is not important. Having only a few number of files at this step will make the reduce operation faster.
“ASVMITI” is the storage mechanism offered by Microsoft. One of the benefits of this storage is the persistence. The SLA that is offered to the clients will offer us the data persistence and access of all information, even if we will stop or delete our HD. This is great, because after the process of data ends, we will be able to access all this data. Don’t forget that storing data into cloud is very cheap. As input, we can use any kind of data, even archives of type gzip, bz2 or deflate.
The last 5 posts were only a small summary of things that were presents at TechEd Europe. A lot of interesting news and information was shared at TechEd. All the sessions can be viewed on Channel 9.

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…