We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Huge file size after doing baseline - for 600 tasks the xml file size generated is 428MB

Hello,


In our project we are doing the following operation to speed up the process of upload and reading of MPP files.

STEP 1: We take the uploaded MPP convert it to aspose project and set the project as baseline.

Aspose.Tasks.License tasksLicense = new Aspose.Tasks.License();
tasksLicense.SetLicense(“Aspose.Total.lic”);
var testFile = @"\600Tasks.mpp";
Project projectPlanNew = new Project(testFile);
projectPlanNew.SetBaseline(BaselineType.Baseline);

STEP 2: Take the baseline project and save it to XML so that we can serialize XML to byte array and save it in database.
projectPlanNew.Save(@"\Test1.xml", SaveFileFormat.XML);
string xmlString = System.IO.File.ReadAllText(@“E:\Work\Sample\TestMPP\TestMPP\LIB\Test1.xml”);
var projectXMLStringToByteArray = XmlSerializeToByteArray(xmlString);

var projectByteArrayToString = XmlDeserializeFromByteArray(projectXMLStringToByteArray);


XmlDocument projectPlanXMLDoc = new XmlDocument();
projectPlanXMLDoc.LoadXml(projectByteArrayToString);


projectPlanXMLDoc.Save(@"\Test2.xml");

During this process the file size is huge based on the number of tasks. For a 600 task mpp file (1MB) the xml converted file after project baseline is around 428MB.

If we do not do baseline the file size is somewhere around 2MB.

This is causing lot of performance issue in the application as every time we need some data from the Project byte array we will need to deserialize this file and get the data.

Please help!!

NOTE: Sample mpp file and code used is attached for your reference.


Hi Sanjay,


Thank you for writing to Aspose support team.

I have also observed this behavior and logged it under id:TASKSNET-1675 for further investigation by the product team. You will be automatically notified once any update is received in this regard.

Hello Kashif,


Any update on this ?

Hi Sanjay,


Thank you for writing to us again.

I have checked the status of this ticket and it is still in the queue for analysis. It may take little time to resolve this issue due to its complexity. I will write back here as soon as some feedback is received in this regard.

The issues you have found earlier (filed as TASKSNET-1675) have been fixed in this update.


This message was posted using Notification2Forum from Downloads module by Aspose Notifier.