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

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 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.51EF 6.0.2VS2013
It seems that there …

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

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

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