mprjDocument.CalculateCriticalPath()

Hi,

Using 4.5.0, the XML task order is now ok. I’ve decided to check the CriticalPathCalculation function.

I am using a sample project that creates an XML file that opens in MS Project. When I add the CalculateCriticalPath function before saving the XML, the calculation routine hangs with no way to determine what is causing the error. Is there a way to stop the calculation once started? Are there some events that should be added to identify errors with the calculations (possibly related to constraints being violated (as in MS Project)?).

To recreate the problem with CalculateCriticalPath, I’ve attached my test routine and the XML file causing the problem.

I’ve made the following changes:

Project_FileSaveAs: added mprjDocument.CalculateCriticalPath()

AsposeTest_SETUP: Commented out: 'xxx Aspose_Test()

Open the file: EventDP2_MSP_RW_701.XML

The calculation loops somewhere in this file. I’m assuming that you can find why the file is looping through your analysis of the calculation.

Regards, Bruce

Hi Bruce,

Thank you for using Aspose.Tasks and your patience.

I have modified your provided test routine and included it in the Main method of my sample console application to reproduce the issue. I can observe that with your input file, the program hangs for about 4-5 minutes and then comes to normal mode. I have used the following lines of code to test the issue at my end:

Dim mprjDocument As Aspose.Tasks.Project
Dim mstrMSPSourceFullPathName As String = "EventDP2_MSP_RW_701.XML"

Sub Main()
Dim license As Aspose.Tasks.License = New Aspose.Tasks.License()
license.SetLicense("K://Aspose.Total.Product.Family.lic")
Dim projectReader As Aspose.Tasks.ProjectReader = New Aspose.Tasks.ProjectReader()
mprjDocument = projectReader.Read(mstrMSPSourceFullPathName)
mprjDocument.CalcTaskIds()
mprjDocument.CalcResourceAssignmentIds()
mprjDocument.CalculateCriticalPath()
mprjDocument.CalcResourceIds()
mprjDocument.CalcResourceStartFinish()

mprjDocument.LastSaved = Now
Dim projectWriter As Aspose.Tasks.ProjectWriter = New Aspose.Tasks.ProjectWriter()
projectWriter.Write(mprjDocument, "New_Plan_Test_MSP_501_SAVE.xml", Aspose.Tasks.TasksDataFormat.XML)
End Sub

We will further investigate this issue and log it in our database for our development team to look into it for further assistance.

Hi Bruce,


Thank you for your patience.

After further testing, I have forwarded your provided details to our development team for further investigation. Once we have any update from our development team in this regard, we will let you know here. The issue has been logged in our Issue Tracking System as: TASKS-33206.

Hi,

Many thanks for testing the sample. The sample is a simple plan for a training course for ‘product based planning’.

As you can guess, taking 4-5 minutes for a simple project is not really acceptable.

As you can see from the sample, there are quite a lot of hierarchical elements in the plan … stages, work packages, products, etc.

FYI: I have found that taking a ‘recursive’ approach to navigate the hierarchy makes the calculations a lot easier. I’ve also found a recursive approach to traversing the links is also a lot easier.

If you do have any information from the developers, I’d be interested to hear. This issue and the other mpp issue that is not resolved is blocking my resuming testing.

Regards, Bruce

Hi,

At a minimum, if there is an error … like the MPP issue that crashes. If you make Aspose.Tasks, just ignore the function (or report an error and skip writing to the file) or fail gently, I can continue to test.

Changing the code to ignore the error or continue will allow me to continue testing the existing MPP functionality. (otherwise, it will be a 3+ month delay).

Regards, Bruce

Hi Bruce,


Thanks for being patient towards the resolution of this issue.

I have just checked the status of this issue from our issue tracking system and found that our development team is looking into it for quick resolution so as to include it in upcoming release.

I have also logged your feedback/concerns against this issue and will share any findings/ETA regarding the resolution of this issue as soon as there is an update from our development team in this regard.

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


This message was posted using Notification2Forum from Downloads module by aspose.notifier.