Skip to main content

Cum sa utilizam optiunea de Pinned Site pe IE9 impreuna cu Windows 7

A fost lansat IE9. Ca de obicei, uni sunt pro, alti sunt contra. Ce m-a facut sa instalez IE9 a fost opțiunea de pinned site. Daca pana acuma doar pe o aplicatie puteai sa faci pin/unpin, IE9 ne ofera aceasta posibilitate si pentru siturile care suporta acest lucru. Chrome are aceasta opțiune de ceva vreme, dar va spun sincer ca nu am remarcato pana acuma( FF fan here).
De ce meta date avem nevoie ca sa putem face ca o pagina web sa poata fi pinned:
  • application-name: numele la pagina. Daca acesta nu este setat se folosește titlul la pagina;
  • msapplication-tooltip: textul care se afiseaza cand esti cu mouseul peste shortcut;
  • msapplication-starturl: URL spre care duce pagina pe care a fost făcuta pinned( de exemplu daca folosti un master page, puteti face orice pinned sa duca spre prima pagina;
  • msapplication-navbutton-color: culoarea la fundal si la text;
  • msapplication-window: dimensiunile default la browser cand se da click pe shortcut;
Toate acestea sunt opționale, ajunge doar sa apelam metoda JS pe care am descriso la sfîrșitul postului. Exemplu:
<meta name="application-name" content="Sample Site Mode Application"/>
<meta name="msapplication-tooltip" content="Programing issues"/>
<meta name="msapplication-starturl" content=""/>
<meta name="msapplication-window" content="width=1024;height=800"/>
<meta name="msapplication-navbutton-color" content="white"/>

In cazul in care doriti sa specificati si o anumita icoana puteti sa folosti:
<LINK rel="shortcut icon" type=image/x-icon href="[locatia_de_pe_server_unde_este_icoana]">
<LINK rel=icon type=image/ico href="[locatie_icoana]">

Atentie: Trebuie sa specificați in primul tag locatie web unde se poate gasi fisierul, iar in al doilea tag se specifica calea relativa. Exemplu:
<LINK rel="shortcut icon" type=image/x-icon href="">
<LINK rel=icon type=image/ico href="./raduIco.ico">

In cazul in care acesta icoana nu este specificata se va folosi cea default a IE9. Userul poate sa personalizeze fiecare site pinned.
Pentru fiecare site pinned putem sa definim anumite taskuri in lista de "jump list tasks". Aceata lista se va afisa cand userul o sa dea click dreapta pe "pin"( nu am gasit o traducere care sa sune bine la pin- ac, bolt, cui, tinta? Suna prea ciudat). Pentru acest lucru putem sa ne folosim de meta data denumita msapplication-task. Prin acest mecanism putem sa oferim un meniu utilizatorului care sa il duca pe acesta la paginile principale( pagina de news, setari cont, status comenzi etc).
<META name="msapplication-task" content="name=Pagina logare;action-uri=;icon-uri="/>
<META name="msapplication-task" content="name=Stiri;action-uri=;icon-uri=http://host/newsIcon.ico"/>

Pentru a se putea face pin la un site ajunge ca intr-o ancora sa apelasi metoda msAddSiteMode().
<a onclick="window.external.msAddSiteMode();" href="#">Pin Me</a><br />

Pentru a verifica daca pagina curenta a fost sau nu lansata ca si un pinned site puteti folosi window.external.msIsSiteMode().
Pentru mai multe informatii recomand:


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

Run native .NET application in Docker (.NET Framework 4.6.2)

The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…