Handle XmlException in ResolveCentralPackageVersion

[Copilot]

ProjectRootElement.Open() can throw XmlException on malformed Directory.Packages.props files, but the catch filter in ResolveCentralPackageVersion only covered IOException and InvalidOperationException, causing an unhandled exception instead of continuing the directory tree walk.

Changes

• ProjectParser.cs: Added XmlException to the exception filter, matching the pattern already used in BuildGraphUseCase

// Before
catch (Exception ex) when (ex is IOException or InvalidOperationException)

// After
catch (Exception ex) when (ex is IOException or InvalidOperationException or XmlException)

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Pull request overview

Updates the core project parsing logic to be more resilient when resolving Central Package Management versions from Directory.Packages.props, specifically ensuring malformed XML doesn’t crash the directory-walk resolution.

Changes:

• Extend the exception filter in ResolveCentralPackageVersion to also handle XmlException.
• Add System.Xml import to support the new exception type.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.