Skip to main content

Cum sa salvezi un stream direct intr-un fisier

Cred ca este a 2-a oara când întâlnesc aceasta cerința in decurs de câteva săptămâni.
Se da un stream și o locație unde trebuie salvat, se cere să se salveze conținutul la stream in locația data. Din păcate API-ul de .NET nu ne permite să facem acest lucru doar dintr-un apel.
O soluție propusa este următoarea:
        /// <summary>
/// Save the stream to the given location.
/// </summary>
/// <param name="stream">The stream.</param>
/// <param name="filePath">The file path where is saved.</param>
/// <param name="blockSize">The size of the buffer(in kB)</param>
public static void SaveStream(this Stream stream,String filePath,SeekOrigin seekOrigin=SeekOrigin.Begin,int blockSize=1)
//Set the poinder to the begin of the stream.
if(stream.CanSeek && seekOrigin==SeekOrigin.Begin)
stream.Seek(0, SeekOrigin.Begin);

//Removed the existing file.
if (File.Exists(CommandLineArguments.Instance.File))

//Save the stream to the given location.
using (var streamWrite = File.Create(CommandLineArguments.Instance.File))
byte[] buffer = new byte[1024*blockSize];
int read;

while ((read = stream.Read(buffer, 0, buffer.Length)) > 0)
streamWrite.Write(buffer, 0, read);
Iar un exemplu de utilizare:
Stream stream=...;
In funcție de necesitați acest exemplu se poate extinde. Din păcate nu putem să facem un extension method pe File deoarece este o clasa statica.


  1. File.Create suprascrie fisierul daca exista, nu e nevoie sa il stergi inainte. Prefer sa folosesc File.Open, in loc de File.Create, pentru ca File.Create foloseste by default FileShare.None, ceea ce inseamna ca nu pot sa ma uit prin fisier in timp ce el este scris sau nu il pot copia daca s-a oprit in vreo exceptie si totusi vreau sa pastrez continutul deja scris.
    Apoi merita mentionat ca in .Net 4.0 Stream are o metoda CopyTo(anotherStream) care ar simplifica mult metoda.


Post a Comment

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…