Skip to main content

InitializeComponent CLR error in Windows 8 Metro application

Daca incercati sa scrieti o aplicatie Metro pentru Windows 8 mai mult ca sigur o sa folositi convertoare la binding. Acestea, in general se definesc in App.xaml in zona de resurse sub forma urmatoare:
<Converters:MyConverter x:Key="myConverter"/>
In pagina voastra o sa puteti sa folosti convertorul pe care l-ati definit in felul urmator:
<Button x:Uid="myButon" Visibility="{Binding IsOpen, Converter={StaticResource BoolToVisibilityConverter}}" Click="OnClick"/>
La compilare nu o sa apara nici o eroare, dar la rulare o sa aveti o surpriza extrem de neplacuta. Pe metoda "InitializeComponent();" aplicatia o sa crape cu o eroare extrem de urata. Continutul erori nu o sa va zica prea mult despre cauza acesteia.
Aceasta problema apare pe Windows 8 RC impreuna cu VS2011 BETA. Solutia pe care am gasito la aceasta problema este sa adaugam definitia convertorului in fiecare pagina unde avem nevoie de acesta.
<Converters:MyConverter x:Key="myConverter"/>
Sa speram ca aceasta problema se va rezolva in versiunea finala.


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 …

Run native .NET application in Docker (.NET Framework 4.6.2)

The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

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…