Handling Exceptions

Handling Exceptions While Working with Microsoft Project Files

When working with Microsoft Project (MPP) files using Aspose.Tasks for .NET, you may occasionally encounter exceptions due to unsupported features or unexpected project structures. In some cases, customers may prefer not to share project files for troubleshooting on our Support forums.

To assist in diagnosing such issues locally, the TasksReadingException class provides a LogText property. This property contains a textual log that can help identify the part of the project that triggered the exception—such as a specific task, resource, or resource assignment.

After isolating the problematic section using LogText, you may attempt to resolve the issue in your project file manually. Alternatively, you can extract and copy only the affected data to a separate project and share that with our support team if further assistance is needed.

The example below demonstrates how to catch and analyze a TasksReadingException when loading a project file:

Project project;
try
{
    project = new Project("New Project.mpp");
}
catch (TasksReadingException ex)
{
    Console.WriteLine("Message:");
    Console.WriteLine(ex.Message);
    Console.WriteLine("Log:");
    Console.WriteLine(ex.LogText);
    if (ex.InnerException != null)
    {
        Console.WriteLine("Inner exception message:");
        Console.WriteLine(ex.InnerException.Message);
    }
}

In this example, the LogText provides detailed insight into what went wrong during the project load operation. Additionally, inspecting the InnerException (if present) may reveal lower-level errors that contributed to the failure.

By using these diagnostics, developers can more effectively investigate issues without exposing sensitive project data. This approach improves troubleshooting while maintaining full control over proprietary information.