Skip to main content

ASP.NET Sprites

Cand trebuie sa cream designul unui site avem nevoie de o mulțime de imagini. Pentru a scadea numarul de apeluri la server, putem sa încărcam aceste imagini inline( conținutul binar a imaginii se poate pune direct in HTML sau CSS, ca si in exemplul de mai jos:
.logo-png
{
width:310px;
height:155px;
text-decoration:none;
display:block;
background: url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAATYAAACb…
}
Dezavantajul la aceasta solutie este faptul ca doar browserele mai noi suporta acest lucru( IE8+,FF 3.5+). Daca trebuie sa incarcam pagini de dimensiuni mari atunci aceasta solutie nu este tocmai buna, deoarece utilizatorul trebuie sa astepte pana cand se incarca tot continutul pentru a putea afisa partial pagina.
Pentru a rezolva aceasta problema aparuta, imaginile se pot pune intr-o singura imagine, iar prin intermediul CSS-ului sa afisam doar o portiune din imagine. Click pentru mai multe informații.
Dar ar fi frumos sa putem pune toate imaginile intr-un singur director din proiect, iar la compilare sa generam automat aceste imagini sprite care sa contina colectia de imagini. In ajutor pentru acest lucru ne vine Sprite and Image Optimization Framework Preview 2.
Pentru al putea folosii trebuie sa cream un director cu numele App_Sprites( putem configura si un alt director). In aceasta locatie adaugăm toate imaginile pe care dorim sa le procesam ca si sprites.
Apoi trebuie sa adaugam in web.config:
<system.webServer>
<modules runAllManagedModulesForAllRequests="true">
<add type="Microsoft.Samples.Web.ImageOptimizationModule"
name ="Microsoft.Samples.Web.ImageOptimizationModule"/>
</modules>
</system.webServer>
Optimize="true" />
Urmatorul pas este sa adaugam un fisier cu numele settings.xml in care sa definim urmatori parametrii:
  • FileFormat - tipul de imagine care se va genera la sfarsit;
  • MaxSize - imaginea maxima a unui sprite, cand aceasta dimensiune este depasita se genereaza un nou sprite;
  • Base64Encoding - daca e setat pe TRUE, continutul imaginilor este adaugat inline( chiar daca este setat pe TRUE, se genereaza sprite-urile pentru browserele ce nu suporta acest mecanism;
  • Quality - nivelul de compresie a imaginii generate;
  • BackgroundColor - culoarea de fundal la sprite( in format ARGB);
Exemplu:
<ImageOptimizationSettings>
<FileFormat>jpg</FileFormat>
<Base64Encoding>false</Base64Encoding>
<Quality>100</Quality>
<BackgroundColor>FFFFFF</BackgroundColor>
<MaxSize>1024</MaxSize>
</ImageOptimizationSettings>
Daca avem mai multe subdirectoare, putem defini cate un fis. de configurare pentru fiecare subdirector. Pentru a adauga o imagine in pagina este nevoie sa folosim controlerul SpriteImage:
<asp:SpriteImage ID="casaSpriteImage"
runat="server"
ImageUrl="~/App_Sprites/images/casa.png"
Optimize="true" />
Gata, fara batai de cap avem acum sprites. Nu mai trebuie sa facem manual adaugarea imaginilor in imaginea folosita pentru sprite si nici nu mai este nevoie sa ne definim CSS-ul manual.
Si acum cum funcționează: La pornirea aplicatiei, se genereaza automat imaginile de tip sprite din directorul App_Sprites( sau din cel specificat). La modificarea folderului App_Sprites, framework-ul detecteaza schimbarea si regenereaza sprites si css-ul pentru acesta.
In functie de setari la client ajunge un img care contine inline continul binar sau un tag ce are setat o clasa CSS ce defineste sprite-ul. Este bine de stiu ca daca avem cache-ul activ continul inline nu se adauga la img ci la CSS( pentru a nu aduce pe client continul binar a unei imagini de doua sau mai multe ori).
Ceea ce trebuie stiut este ca acest framework poate fi folosit in proiectele de tip: ASP.NET, MVC si Razor. In cazul meu a funcționat fara probleme.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

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.51 EF 6.0.2 VS2013 It see

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too