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(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP