Taking lots of time to load MPP / XML file in our wpf (Prism) but same file loaded fast in console application

Hi Team,

We are unable to figure out the problem we are using apose.task 9.2.1.0 dll in our WPF (Prism) application, this is taking too time to load mpp / xml file in our application,
even I am checking the same file with same dll file in console application this is loading with 15 to 20 second.
When I Running the code in main thread then it will be fast. but when I am running same code in worker thread the loading time is near 2 minutes.

following is my code
Project proj = null;
proj = new Project(filepath);

Please kindly provide me some help.

With Regards,
Manoj kumar choubey.

Hi Manoj,


Thank you for writing to Aspose support team.

I have tested the scenario by creating a WPF(Prism) application and loaded a project file with 5000 tasks. It took about 2.3 seconds to load which is equal to the time taken by a desktop application. It seems to be a specific issue and needs further investigation, Please share your sample application along with the project file which is used for testing. We will re-produce the scenario here and provide assistance accordingly.

Hello Kashif,


I have identified the issue that is causing a delay in loading of the project.
We have procured a license for Aspose Tasks and when I set the license as below, subsequently loading a mpp file is taking a lot time (3 - 4 minutes).
Commenting out the SetLicense call, loads the project in about 7-9 seconds.

Aspose.Tasks.License license = new Aspose.Tasks.License();
license.SetLicense(“Aspose.Tasks.lic”);

Regards
Manoj

Hi Manoj,

Thank you for writing to us again.

I am afraid that I could not re-produce the scenario here in WPF (Prism) application by adding and not adding the license. Please have a look at the attached project which loads a project with 5000 tasks. It takes less than 2 seconds to load the project with and without the license.

You may please send us a simple project which can be used here to observe the problem with and without the license.

P.S. Project is loaded in the following function:
private void
InteractionRequestView_Loaded(object sender, RoutedEventArgs e){ }

Hi Kashif,



I have tested by my .mpp file with license file, this is taking near about 1 minute 30 second by your given application.
Please find the attached file of our mpp file, and also send me your .mpp file so I can test in our application.


With Regards,
Manoj

Hi Manjo,

Thank you for sharing your sample MPP file that helped us reproduce the issue at our end. We have logged it as TASKS-34525 in our issue tracking system for further investigation by our Product team and will update you here once there is some information available in this regard.

Hi Kashif,



Thank you for logging issue, I am waiting for your replay. So we can do next things.


With Regards,
Manoj

Hi Manoj,

You are welcome. We’ll keep you informed as and when there is some update available in this regard.

Hi Kashif,



We have procured a license and this is a showstopper. Till this is fixed do you a work around ?


With regards,
Manoj

Hi Manoj,

We are sorry for the inconvenience you are facing. Our Product team is investigating the issue and there is no update available about the ETA of this problem till yet. We’ll update you here as soon as there is some information available in this regard.

Hello Team,


Any update on the issue. My developer is still awaiting for your response.
This is a big impediment in our development.

Regards

Hi Manoj,

The issue has been planned to be fixed in the upcoming version of Aspose.Tasks for .NET API that is due for release by the end of April. We’ll update you here once the fix version is available for download.

Hi,


Do you have an update on this. Still awaiting for a fix.

Regards

Hi,

The issue has been fixed and the upcoming version of Aspose.Tasks for .NET 9.4.0 will incorporate this fix for you. We’ll notify you here once the fix version is available in this regard.

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


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