Skip to main content

Get current position in Metro app on Windows 8 freeze

Ati incercat pana acuma sa obtineti locatia GPS curenta intr-o aplicatie Metro pentru Windows 8?
Daca nu, trebuie sa stiti ca nu e deloc complicat, este chiar la mintea cocosului API-ul.
Geoposition currentPosition = await new Geolocator().GetGeopositionAsync();
Toate informatiile necesare o sa le puteti gasi intr-un obiect de tip Geoposition. Intr-o aplicatie simpla totul o sa mearga fara nici o problema. Apoi o sa ajungeti sa creati un provider de genul GPSProvider. Fiind o metoda asincrona, aceasta metoda o sa fie apelata cu await, iar codul vostru o sa arate in felul urmator:
public class GPSProvider
{
    public async Task<Geoposition> GetCurrentPositionAsync()
{
    // some code.
    return async _geoLocator.GetPositionAsync();
}
}
In unele cazuri, cand o sa rulati codul pe un alt thread decat cel principal o sa va treziti ca locatia GPS nu poate sa fie rezolvata, codul ingheata la metoda GetPositionAsync(). Cauza pentru care se intampla acest lucru este ca codul nu ruleaza intr-un mediu MTA (Multi Threaded Apartment) si nu intr-un mediu STA (Single Threaded Apartment).
Aceasta problema apare doar la primul apel, dupa acest apel, metoda poate sa fie apelata din orice locatie fara nici o problema. In specificatiile la acesta metoda se precizeaza ca aceasta trebuie sa fie apelata prima data dintr-un mediu STA, iar apoi o sa functioneze si dintr-un mediu MTA. In spate aceasta metoda apeleaza la randul ei un COM, din aceasta cauza apare aceasta restrictie.
From MSDN:
In apps that use C# or C++ in Windows 8 Consumer Preview, the first use of the Geolocator object to call GetGeopositionAsync should be on the STA thread. Calls from an MTA thread may result in undefined behavior.

Comportamentul este destul de ciudat si neasteptat. Solutia la aceasta problema este sa mutati codul care face apel la metoda GetPositionAsync in xaml.cs sau in orice loc care sa va asigure ca sunteti intr-un mediu STA. O alta solutie este sa va definiti o metoda de warm up, care este apelata din App.xaml.cs de exemplu.

Comments

  1. I like the valuable info you provide in your articles. I will bookmark your blog and check again
    here frequently. I'm quite certain I'll learn many new stuff right here! Best of luck for the next!
    My page: restore contacts Microsoft exchange server

    ReplyDelete

Post a Comment

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 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 …

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.
publ…