Skip to main content

Metro UI and Windows Metro Style Application is not the same thing

Am inceput sa vad o greseala care se face destul de des. Lumea a inceput sa incurce Metro UI cu Windows Metro Application. Acestea sunt doua lucruri total diferite.
Metro UI este un set de reguli care definesc modul in care interfata grafica a unei aplicatii arata. Acesta are la baza stilul "Swiss" care a fost dezvoltat in Elvetia la inceputul anilor 1950. Stilul Swiss a fost dezvoltat pentru ziare si reviste. Pe baza acestuia a fost definit Metro UI care a aparut odata cu Windows Phone, iar acuma urmeaza sa fie folosit si pe Windows 8. Este bine de stiut ca acest style poate sa fie facut pentru orice fel de aplicatie si in orice limbaj (Windows Forms, WPF, SL, HTML and so on). Exista un set de reguli pentru stilul Metro, iar Microsoft a definit reguli clare si precise pentru a exista o fluiditate intre aplicatii.
Windows Metro Application sau Windows Metro Style Application este tip de aplicatie care o sa ruleze pe Windows 8. Aceste tip de aplicatii trebuie sa fie scrise intr-un anumit fel astfel incat sa nu consume foarte multe resurse. Din aceasta cauza API care este accesibil intr-o aplicatie Metro este foarte diferit fata de cel pe care il avem cand folosim .NET 4.5. Din punct de vedere a UI-ului aceste aplicatii trebuie sa aibe Metro UI. Acest tip de UI este suportat in totalitate de catre API.
Pe PC-uri normale sau pe laptop o sa putem avem versiunea normala de Windows 8. Pe aceasta vs. o sa poata sa fie rulate aplicatii clasice care mergeau si pe Windows 7. Windows Services o sa existe in continuare. In schimb, din cate am vazut pana acuma pe tablete cu Windows 8 nu sa putem rula aplicatii clasice, ci doar aplicatii Metro Style Application. Aceasta versiune se numeste Windows RT si o sa ruleze pe procesoare ARM si WOA.
In concluzie, putem sa avem pe orice device si in orice limbaj Metro UI, dar in acest moment doar pe Windows 8 putem sa avem aplicatii Windows Metro Style.


  1. Foarte bine punctat.

  2. Normal ca Metro UI e doar un set de reguli de design, si teoretic se pot implementa pe orice platforma, da' ma cam indoiesc ca il vom vedea pe altceva inafara de plaforma Windows > 7 si website-urile Microsoft :) ..


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 …

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.

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…