Skip to main content

Windows 8 for tables and viruses

Ieri seara am participant la un eveniment unde s-a prezentat si Windows 8. De data asta eram pe partea cealalta a baricadei (ca si participant), dar am vazut ca lumea spune destul de des:
Abia astept sa apara virusi pentru Windows 8.
Din acest punct de vedere, pentru versiunea normala de Windows 8 mai mult ca sigur o sa existe (din pacate), nu avem ce face. Dar pentru Windows 8 RT, versiunea care este destinata tabletelor, s-ar putea sa nu avem surprize nefericite.
In primul rand fiecare aplicatie ruleaza intr-un sandbox si nu poate sa faca foarte multe schimbari. Fiecare aplicatie inainte sa ajunga in store este supusa la niste teste, unde se testeaza cat de sigura este pentru utilizator.
Daca aceste verificari o sa se faca cum trebuie s-ar putea sa nu avem probleme cu aplicatiile. De exemplu pentru Windows Phone 7 nu am auzit de nici o problema de acest gen.
Deja, foarte multe compani care creaza antivirusi pentru Windows, isi pregatesc si ultimele versiuni de soft pentru Windows 8, iar pentru Windows 8 RT sper sa nu avem probleme sau cel putin asa ma astept eu.


  1. Unde ai fost? Pregatesc un blogpost ...

    1. La o prezentare tinuta de una dim companiile IT din Cluj-Napoca

  2. Nu mi-as face mari sperante - cum din cate stiu pe versiunea de Win8 pentru tablets non-ARM se vor putea rula aplicatii normale, non-"metro", malwares vor aparea.
    La fel si pe ARM - daca va exista o posibilitate de side-loading (chiar daca teoretic doar pentru enterprise-stuff), va exista in timp si malware.


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…