DEV Community: panchenko-dm-aspose

Open or create TAR files in C# with Aspose.ZIP

panchenko-dm-aspose — Sun, 25 Apr 2021 14:11:51 +0000

Prerequisite – C# ZIP Library

Aspose.ZIP for .NET is a powerful and easy-to-use API for zipping or unzipping files and folders within .NET applications. It supports all the most popular ZIP formats and provides AES encryption techniques to encrypt the files in ZIP archives. You can install the API from NuGet or download its binaries from the Aspose Downloads section.

How to create a TAR in .NET

The next part of the code demonstrates the creation of a new TAR archive:

using (var archive = new TarArchive())
{
    archive.CreateEntry("alice29.txt", File.OpenRead( "alice29.txt"));
    archive.Save("Archive.tar");
}

That's all, after 3 lines of code the TAR archive has been saved to the disk!

Other TAR standards.

There are several different TAR standards: ustar, GNU tar, pax and V7. Ustar format is the default implementation for the most Windows applications, while GNU tar is the default for Linux command shell. Aspose.ZIP currently supports ustar and GNU tar. The Aspose.ZIP library creates archives in ustar format by default. To create a GNU tar archive the TAR format must be explicitly specified:

using (var archive = new TarArchive())
{
    archive.CreateEntry("alice29.txt", File.OpenRead( "alice29.txt"));
    archive.Save("Archive.tar", TarFormat.Gnu);
}

Ustar vs GNU Tar. What's the difference?

In what cases it’s better to use GNU tar than ustar?

Ustar has some limitations compared to GNU tar, for example, ustar doesn’t support entries with names more than 100 characters, the total size of the archive can’t be more than 8 Gb. If created tarball isn’t fit for these restrictions Aspose.ZIP will save the archive in GNU tar format even without passing TarFormat.Gnu in Save method.
Another difference between standards is that GNU tar supports saving sparse files in the archive.

Compress TAR using GZip.

Tarball can be compressed to GZip using Aspose.ZIP:

using (FileStream tarGzStream = File.OpenWrite("Archive.tar.gz"))
{
    using (var archive = new TarArchive())
    {
        archive.CreateEntry("alice29.txt", File.OpenRead("alice29.txt"));
        archive.SaveGzipped(tarGzStream);
    }
}

Learn more about Aspose.ZIP for .NET

Aspose.ZIP provides features to work with many other zip standards. Written totally on managed code Aspose.ZIP will be a good choice for applications that run on different OS.
Explore more about our C# ZIP API using the following resources:

Check what Aspose.ZIP is capable of with our free web-apps that are completely based on Aspose.ZIP for .NET:

ZIP files in C# using Aspose.ZIP parallel compression

panchenko-dm-aspose — Thu, 25 Feb 2021 08:31:57 +0000

Prerequisite – C# ZIP Library

Aspose.ZIP for .NET is a powerful and easy-to-use API for zipping or unzipping files and folders within .NET applications. It also provides AES encryption techniques to encrypt the files in ZIP archives. You can install the API from NuGet or download its binaries from the Downloads section.

Classic way of creating ZIP archive in Aspose.ZIP for .NET

The classic way means that we compress files within a data folder one by one and do not take any advantage of having a multicore CPU.

using (FileStream zipFile = File.Open("archive.zip", FileMode.Create))
{
      using (Archive archive = new Archive())
      {
          archive.CreateEntry("first.bin", File.OpenRead("data1.bin"));
          ...
          archive.CreateEntry("last.bin", File.OpenRead("dataN.bin"));
          archive.Save(zipFile);
       }
}

Parallel compression with Aspose.ZIP for .NET

Aspose.ZIP allows you to utilize all of your CPU cores using ParallelOptions. Let's look at the code first:

using (FileStream zipFile = File.Open("archive.zip", FileMode.Create))
{
    using (Archive archive = new Archive())
    {
        archive.CreateEntry("first.bin", File.OpenRead("data1.bin"));
        ...
        archive.CreateEntry("last.bin", File.OpenRead("dataN.bin"));
        archive.Save(zipFile, new ArchiveSaveOptions()
           {
             ParallelOptions = new ParallelOptions() 
             { ParallelCompressInMemory = ParallelCompressionMode.Always }
           });
    }
}

Setting ParallelCompressInMemory indicates the strategy we choose to multitask.
Here are three options:

ParallelCompressionMode.Never: compression of all entries is sequential. Only one CPU core works on compression and flushes compressed data as it comes.
ParallelCompressionMode.Always: It forces compression of entries in different threads regardless of entry size, available memory, and other factors. Each CPU core simultaneously compresses a file keeping its compressed data in RAM. Upon the entry is compressed it flushes to the result stream. If your RAM amount is small and the total size of some N entries (where N is the number of CPU cores) is huge it may happen that all RAM available for CLR will exhaust and OutOfMemoryExcepton arises.
ParallelCompressionMode.Auto: It estimates CPU cores, sizes of entries, available memory and chooses whether to compress entries in parallel or sequentially. In this mode some smaller entries to be compressed in parallel while others sequentially. LZMA entries are not compressed in parallel because of high memory consumption. Generally, it is safe to go with this option, Aspose.ZIP is wary with estimations and switches to sequential compression as a fallback. There is one more property of ParallelOptions for this mode - AvailableMemorySize. It is pointless for any other mode. Roughly speaking, it is the high limit of allocated memory while compressing entries with all CPU cores, in megabytes. Aspose.ZIP uses that number to estimate the biggest size of entry which is safe to be compressed in parallel. Entries above the threshold to be compressed sequentially. AvailableMemorySize is a double-edged sword: being set too high with huge entries, it can produce RAM exhaustion, intense swap, and even might be out of memory exception. Being set too low, most of the entries will be compressed in a sequential way without much speed-up. So, sophisticated users can assign it considering trade-off.

We encourage you to play with different modes of parallel compression on your typical data to determine what is the best settings in your case.

Learn more about Aspose.ZIP for .NET

Explore more about our C# ZIP API using the following resources:

Check what Aspose.ZIP is capable of with our free web-apps that are completely based on Aspose.ZIP for .NET:

Export/Import Excel documents to MS Project in C#/.NET using Aspose.Tasks

panchenko-dm-aspose — Tue, 23 Jun 2020 12:44:22 +0000

Export MS Project data to XLSX

Sometimes there may be requirements to work with your project data in Microsoft Excel.
In simple scenarios, you can export project data using Aspose.Tasks with two lines of code (default settings will be used):

The resulting spreadsheet will contain three sheets (for Task, Resource, and Assignments) with default columns.
If you need a specific set of columns the resulting spreadsheet can be customized in the following way:

The resulting spreadsheet when opened in Microsoft Excel:

Import project data from XLSX

There is no API for importing XLSX to project data at the moment, but you can use OpenXml to implement an importing routine specific to your data. Here is a simplified example of how it can be done (requires ‘DocumentFormat.OpenXml‘ NuGet package ):

Modify MS Project files in TypeScript or JavaScript using Aspose.Tasks Cloud API.

panchenko-dm-aspose — Thu, 07 May 2020 15:18:31 +0000

Aspose.Tasks Cloud is a REST API for manipulating and converting Microsoft Project (MPP, XML, etc.) and Oracle Primavera (XER) documents. It allows you to work with all aspects of a project as well as offers a wide range of export options allowing developers to convert supported project formats to a number of industry-standard formats (PDF/Excel/Images).
Our Cloud SDKs are wrappers around REST API in various programming languages (PHP, Python, Node.js), allowing you to work with MS Project/Oracle Primavera documents in the language of your choice quickly and easily, gaining all benefits of strong types and IDE highlights.
Before we get started, I want to say a few words about legal use Aspose.Tasks Cloud API. For receiving successful responses from the server, you need to sign up for free on https://id.containerize.com/signup so you can get your own App SID and App Key.
These credentials will be used in a further example. We also will use 'fs' module for read\write files, but you can use whatever is more convenient for you. After you get SID and Key for your app, we will need to install SDK package, just like that:

npm i @asposecloud/aspose-tasks-cloud

When it's done, let's create an instance of Tasks.Api:

Good! Now we can do whatever we want with our project. Let's add a new task:

Simple isn't it?. Now let's look at the result:

Well, that's it. We just tested adding tasks to the project file. But what if you want to add, modify, delete or take calendar from your project? Or do some stuff with your assignments? Or deal with some another part of the project? SDK source code contains a large number of use cases which you can see here.
I hope you enjoy using this tool to manipulate your MS project files.

Save MS Project files into various formats using C# and Aspose.Tasks for .NET

panchenko-dm-aspose — Fri, 17 Apr 2020 09:14:27 +0000

Aspose.Tasks for .NET is a reliable project management API to process Microsoft Project files. API supports reading, writing and manipulating Microsoft Project documents without any other software dependencies.

Presented below is a shorthand article describing how to convert Microsoft Project files (composed in native Project formats: MPP, MS Project XML) into the non-Microsoft project formats: graphical (PNG, BMP, JPEG, TIFF, SVG, PDF), Primavera(Primavera XML, XER).

Create a new Microsoft Project document and save it to other Microsoft Project file formats

Aspose.Tasks for .NET allows to create a project from scratch and convert it into other Microsoft Project file formats (such as Microsoft Project XML, Microsoft Project MPX):

Convert Microsoft Project files into graphical formats

Aspose.Tasks for .NET can read a project file from native project formats (MPP, MPX, Microsoft Project XML) and save it into any of graphical formats: PNG, BMP, JPEG, TIFF, SVG, PDF. There are two main approaches. The first allows a user to easily save a project into any of the available formats by specifying one of Aspose.Tasks.SaveFileFormat enum members:

Another approach is a usage of special setting classes that allow to tune the saving options.

Convert Microsoft Project files into Primavera formats

Along with saving in graphical formats Aspose.Tasks for .NET supports conversion into Oracle Primavera formats (e.g. Primavera XML, Primavera XER):

Convert Microsoft Project files into other formats

Aspose.Tasks for .NET also supports a conversion of project files to HTML, XLS, XLSX, XAML, TXT formats:

How to try

You can try the above-mentioned features with your projects in our free web Aspose.Tasks Conversion app - it uses the same engine under the hood.
The whole set of examples that shows the features of saving project files into various formats are in our GitHub repository. The latest version of Aspose.Tasks for .NET is always available on the official Aspose website or via NuGet package.

Save your projects in C# to Project Server\Project Online via PWA using Aspose.Tasks for .NET

panchenko-dm-aspose — Mon, 06 Apr 2020 08:01:45 +0000

Introduction

Below guide explains how you can manipulate your projects from MS Project Online (Project Web Application) hosted by SharePoint.

Background

The new Aspose.Tasks feature uses Project Web Access (or PWA) API - the same API is used for interaction of Microsoft Project Professional desktop application and Project Online service.

Using the code

Aspose.Tasks for .NET can be added as a NuGet reference from https://www.nuget.org/packages/Aspose.Tasks/

Create project in Project Online account

A project can be created in your Project Online account using the ProjectServerManager class:

Please note that project.Get(Prj.Guid) and project.Get(Prj.Name) properties should be unique within projects in the specified Project Online account.
Projects created in that way can be found in the “Working” store of your Project Online account (see screenshots below). The support of "Published" store will be available in future releases.

You can find the created project and store selection option in Microsoft Project Professional desktop application in “Open Enterprise Project” dialog (“File->Open->Project Web App->Browse” path):

Modify project in Project Online account

Also, you can modify a project in your Project Online account using the following syntax:

Working with on-premise Project Server(2016 or 2019)

Use the following code sample to create, read and update projects in on-premise Project Server (2016 or 2019) using ProjectServerManager class:

How to try

You can try part of the above mentioned features with your online projects in our free web Aspose.Tasks Downloader app - it uses the same engine under the hood. More info can be found in this blog post.