Skip to main content

Copy a directory recursive

Ultima oara cand a fost nevoie sa fac asa ceva a fost in timpul facultății. In seara asta aveam de lucru la un proiect ce se ocupa cu un deploy si supriza, aveam nevoie de acest mecanism. Speram ca .NET 4.0 sa fie plin de surprize, dar din pacate nu. Asa ca am inceput sa implementez de manuta si uite ce a iesit:
public static class DirectoryHelper
{
///
/// Copy recursive a directory to a specific location.
///

/// Source directory.
/// Destination directory.
public static void Copy(string sourceDirecotry, string destionationDirectory)
{
if (!Directory.Exists(destionationDirectory))
{
Directory.CreateDirectory(destionationDirectory);
}
//Copy all files from the current directory.
foreach (string file in Directory.GetFiles(sourceDirecotry))
{
var fileName=Path.GetFileName(file);
File.Copy(Path.Combine(destionationDirectory,fileName), Path.Combine(destionationDirectory, fileName));
}
//Copy files from the subfolders.
foreach (string folder in Directory.GetDirectories(sourceDirecotry))
{
var directoryName = Path.GetFileName(folder);
Copy(Path.Combine(destionationDirectory,directoryName), Path.Combine(destionationDirectory, directoryName));
}
}
}
M-am gandit si la o varianta LINQ, sa folosesc ForEach si expresii lambda, dar nu e la fel de rapid ca un foreach scris de mana. Un For ar fi si mai rapid, dar nu cred ca e cazul, prefer sa las codul sa fie cat mai usor de inteles. Avantajul la LINQ ar fi fost ca se poate scrie fara apeluri recursive( o sa revin maine si cu varianta aceasta).
Dezamagirea mea a fost in momentul in care am vrut sa il pun ca extension method la System.IO.Directory. Nu se poate asa ceva din cauza ca System.IO.Directory este o clasa statica. Asa ca trebe sa ne multumim cu clase helpere sau sa adaugam aceasta metoda ca extensie la DirectoryInfo.

Atentie, codul nu functioneaza daca unul din path-uri este subpath pentru celalat path. In cazul meu validarea pentru acest caz se face in alt loc.

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 provided a too