Skip to main content

URI in Windows 8 Metro Style App

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""));



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