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

How to audit an Azure Cosmos DB

By
In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...
Post a Comment
Read more

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

By
Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...
Post a Comment
Read more