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(

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