Skip to main content

.NET framework setup hack

By
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
Labels:

Comments

  1. TudorJanuary 25, 2011 at 7:06 PM

    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

By
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(...
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
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...
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 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 provi...
Post a Comment
Read more