[BUG] Unhandled exception when attempting to run app after VS Code has been open a while

Describe the Issue

Dear C# Dev Kit Community,

I want to address some persistent bugs and suggest improvements for the C# Dev Kit in Visual Studio Code. As a developer using this extension regularly, I've encountered several issues that hinder productivity and overall usability. Here are the problems I've faced:

• Project Loading and Symbol Recognition: Occasionally, the Dev Kit fails to load projects correctly and doesn't recognize symbols throughout the solution. Even after restarting VSCode, this issue persists, sometimes requiring a full system restart to resolve. It's a frustrating experience that interrupts workflow unpredictably.

• Debugging Functionality: The functionality of F5, F10, and F11 during debugging could be more consistent. Despite proper compilation and attempts to run the project, these keys often fail to execute their intended actions, leading to confusion and wasted time in troubleshooting.

• Performance Degradation: With each update, the C# Dev Kit consumes more memory and introduces significant sluggishness to the entire system. This contradicts the original purpose of using VSCode as a lightweight alternative to full-fledged IDEs like Visual Studio.

• Namespace Structure in Solution Explorer: When creating a new class in Solution Explorer, the Dev Kit doesn't follow the folder structure to determine the namespace. This oversight disrupts the organization and makes maintaining a coherent project structure cumbersome.

• Lack of Official File Creation Add-on: It's puzzling why there isn't an official add-on for creating files like classes and interfaces directly from Explorer. Instead, the current implementation in the Solution Explorer feels inadequate and needs to be in sync with user expectations.

• Missing Test Explorer: An official, installable Test Explorer needs to be present. While alternative options exist, the absence of an official solution leaves users searching for reliable testing integration elsewhere.

Suggestions for Improvement:

• Modularize New Features: New features, such as the "Solution Explorer," should be offered as optional add-ons rather than being integrated directly into the Dev Kit. This approach maintains the lightweight nature of VSCode while allowing users to tailor their development environment to their needs.

• Avoid Mandatory Add-ons: While add-ons can enhance functionality, they shouldn't be mandatory installations. Encourage modularity by offering a suite where users can choose which add-ons to install, ensuring a more customizable experience without unnecessary bloat.

As a developer working with .NET applications on various operating systems, including Linux and Windows, these issues persist across different environments. I urge the development team to prioritize resolving these issues and making the C# Dev Kit more user-friendly and efficient.

Let's work together to make the C# Dev Kit in VSCode the best tool it can be for the entire community.

Steps To Reproduce

No response

Expected Behavior

the add-on just work as expected and better than Omnisharp.

Environment Information

Linux (Ubuntu and Manjaro)
Windows 11

The report names no files, tests, or entry points and combines several unrelated C# Dev Kit and VS Code problems. Start by isolating one symptom, especially the unhandled exception after VS Code has been open, and document reproducible steps on the listed environments; completion criteria cannot be determined until a single scope and expected behavior are defined.