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))
//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.


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

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

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…