Skip to main content

Arhivare/Dezarhivare in C#

Am avut zilele astea nevoie de a implementa o modalitate prin care sa dezarhivez un pachet zip intr-o anumita locatie. Toate bune si frumoase, am zis ca nu ar trebuii sa am nici o problema, GZipStream o sa functioneze perfect...
Dar nu a fost asa simplu, problema ca GZipStream stie sa manipuleze doar streamuri, iar daca ai un zip format dintr-o structura de directoare si fisiere nu prea ai sanse sa faca acest lucru out of the box.
O solutie era nevoie sa implementez acest mecanism. As fi putut face acest lucru, dar din punct de vedere a timpului depasea timpul pe care il aveam alocat pentru acest task.
Cautant o libratie deja scrisa, am gasit DotNetZip. O librarie destul de complexe, iti permite sa faci foarte multe lucruri, dar cu un API simplu si foarte usor de inteles.
De ce am ales aceasta solutie? Dupa ce am adăugato la referinta am luat copy/paste codul din exemplele pe care erau la ei pe site si a functionat fara probleme.
De exemplu pentru a adauga ceva in arhiva ajunge sa apelazi .Add(pathFisierului) sau sa indicati spre locatia unde este directorul, iar la sfarsit sa apelasi .Save(numeArhiva).
Iata codul de care am avut nevoie:
using (ZipFile zip = ZipFile.Read(locatieZipString))
{
foreach (ZipEntry fis in zip)
{
zip.Extract(locatieUndeSeCopieazaString);
}
}

Colectiile suporta si Linq, a.i. orice filtrare a fisierelor extrase se poate face foarte usor.
O alta functionalitate care mi-a placut este posibilitatea de a face update la un pachet, sau adaugare/stergere continut din pachet fara sa mai fie nevoie sa dezarhivam pachetul.

Daca o sa aveti vreodata nevoie de o solutie pentru arhivare/dezarhivare pachete zip, va recomand aceasta librarie.
Nota pe care o primeste este 9. Ar fi primit 9.50 daca avea posibilitatea sa dezarhivez un pachet, intr-o anumita locatie fara sa mai fiu obligat sa iterez prin fiecare intrare din pachet.

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 provi...