Skip to main content

URI in Windows 8 Metro Style App

By
Intr-o aplicatie Windows 8 Metro App putem sa specificam printr-un URI locatia de unde sa incarcam continutul unui fisier. Folosirea path-urilor absolute nu este recomandata, deoarece in mod normal nu avem acces la orite path. De exemplu daca folosim un path de forma: "C:\Foo\content.txt" o sa ne trezim cu o eroare de genul "Access is denied".
Este foarte important de stiut ca o aplicatie de tip Metro App are access doar la un numar limitat de locatii. Nu o sa avem access la orice locatie de pe masina. Singura varianta pentru a accesa locatii la care nu avem acces este ca userul sa specifice locatie prin intermediul unui file picker.
URI are urmatoare forma: [scheme]://[numeDomeniu]/[path]
[scheme] poate sa aibe 3 valori predefinite:
  • ms-appx - care va indica locatia unde este pachetul aplicatiei (locatia de unde ruleaza aplicatia)
  • ms-appdata - care indica locatia unde se salveaza datele pe care le-am downloadat de pe internet
  • ms-resource - locatia care contine fisiere de resurse localizabile
Numele de domeniu poate sa fie ignorat, caz in care se va folosii domeniul curent.
In exemplul de mai jos incarcam logo-ul aplicatiei din directorul 'images'.
IAsyncOperation<StorageFile> storageFileAsyncOp = StorageFile.GetFileFromApplicationUriAsync(new Uri("ms-appx:///images/AppLogo.png""));

Enjoy!
Labels:

Comments

Post a Comment

Popular posts from this blog

How to audit an Azure Cosmos DB

By
In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...
Post a Comment
Read more

Can User Technical Profile Influence AI Architecture Decisions?

By
In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
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...
8 comments
Read more