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

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…