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

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...

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.51 EF 6.0.2 VS2013 It see...

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provi...