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.

Comments

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

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

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

    ReplyDelete

Post a Comment

Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

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