windows-8

I am working on Windows 8 (using C#) and when using the async keyword there's a scenario where i can't seem to handle exceptions well. The scenario involves launching an async lambda, posting it to run on the UI thread. Exceptions that occur during the execution of the lambda code gets re-thrown on the calling thread, with no ability to catch them properly. Example: this block of code is executed on some worker thread, and tries to schedule work on the UI thread: await Window.Current.Dispatcher.RunAsync (CoreDispatcherPriority.Normal , async () => { var result = await CurrentAppSimulator

I would like to list blobs in a container. For desktop apps, the Azure Storage SDK provides the following method: CloudBlobContainer container = blobClient.GetContainerReference("myBlob"); container.ListBlobs(); However, using the WinRT library the method is absent (probably due to its blocking nature). What should I use instead? You would need to use ListBlobsSegmentedAsync function on the blob container to fetch the list of blobs. See the code below for example: CloudStorageAccount account = new CloudStorageAccount(new StorageCredentials("accountname", "accountkey"), true); var client =

I have a Windows Store mess around app. I added a Basic Page and it added the Common classes, such as LayoutAwarePage. But Page.OnNavigatedTo doesn't get called when an app starts. The MSDN doc says: Invoked when the Page is loaded and becomes the current source of a parent Frame Which happens during launch. I discovered this when LoadState wasn't being called. Rick Barraza uses LoadState, which is called by OnNavigatedTo, in his demo: http://channel9.msdn.com/Series/Migrating-apps-from-Windows-Phone-to-Windows-8/Binding-the-Interface-in-Windows-Store-apps#time=2m50s I know something is broken