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)

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.


Popular posts from this blog

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

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.