Skip to main content

.NET framework setup hack

Pornim de la problema urmatoare: kit-uriile de .NET devin din ce in ce mai marii. De la 16MB am ajuns la 240MB in .NET 3.5. Ca printr-o minute, kitul de .NET 4.0 este de doar ~50MB(daca nu il deschidem). Dar nu va lasati pacaliti, la dezarhivare o sa ajunga lejer la 250MB.
Ce putem sa facem? Prima masară este ca setup-ul care il alegem pentru client sa nu fie web-installer, deoarece o sa omoram banda la internet intr-o firma mare fara rost. Cel mai bine este sa alegem setup-ul full. Dar nu primul link de download gasit la Microsoft pe site. Acesta de cele mai multe ori include assembly-urile pentru toate versiune de arhitectura a unei masini( x86, x64, ia64). O sa ajungem sa trimitem la client uneori de doua ori mai multe date decat are nevoie.
Totodată existe mai multe versiuni de .NET, una pentru client si una full. Cea pentru client contine assembly-urile folosite intr-o aplicatie client.
O solutie gasiti aici. In functie de arhitectura sistemului si daca aveti nevoie de versiune pentru client sau full o sa gasiti mai multe instalare. Cu cat installer-ul este mai mic, cu atat resursele ocupa pe disk in timpul instalarii si dupa instalare sunt mai mici. De exemplu setup-ul clasic pentru .NET 4.0, care include toate versiunile de .NET 4.0( x86, x64 si ia64) necisita 1019MB, spatiu pe disk liber pe C: in momentul instalării, in comparatie cu versiunea pentru x86 care necesita umpic mai mult de 800MB.
Dar uneori se poate mai mult de atat. Fiecare setup poate sa fie deschis precum o arhiva( cel mai simplu din total commander, cu ctrl + sagetiile stanga/dreapta). In aceasta o sa gasim o structura de directoare. Fiecare versiune de .NET o sa fie intr-un director separat. De exemplu in setup-ul de .NET 3.5 gasim directoare separate pentru .NET 2.0, .NET 3.0 si .NET 3.5.
Daca avem deja o masina cu .NET 2.0 instalat, atunci nu mai este nevoie sa includem in setup si fisierele pentru .NET 2.0. Ajunge sa stergem fisierele directorul de .NET 2.0. Setup-ul o sa ruleze fara probleme. La fel puteti elimina si pachetele pe care credeti ca nu o sa le folositi, de exemplu cele de WCF, in cazul in care aplicatiile care ruleaza pe aceste masini nu folosesc WCF, sau cele pentru x64 sau ia64.
Atentie, aceste modificari trebuie facute cu precautie, iar inainte ca pachetul sa fie trimis la client sa se faca o testare amanuntita.
O alta varianta pentru a deschide un setup este sa il rulati din linie de comanda sub forma:
[numeSetup].exe. /x

Comments

  1. In ziua de azi tot mai multi clienti au .NET-ul deja instalat. Cand aplicatia e distribuita pe CD/DVD oricum dimensiunea installerului nu mai e asa importanta..

    In rest, pentru cine nu vrea sa foloseasca web installer-ul, poate alege varianta potrivita de la:
    http://smallestdotnet.com
    iar kit-ul nu va depasi 35 MB de obicei (server+client ver. x86)..

    ReplyDelete

Post a Comment

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(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP