Visual Studio 2022 - working with 'how to to start debugging' when launching WPF application with .NET 5
Quick question that's been bugging me - I've spent hours debugging this and I've spent hours debugging this and I'm stuck on something that should probably be simple... I'm having an scenario with my WPF application in Visual Studio 2022 where I receive the behavior message 'Unable to start debugging. The start action is not supported.' This happens when I try to run my app after making some recent changes. I have verified that the target framework is set to .NET 5.0, and everything was working fine before I updated some NuGet packages, including `Microsoft.Xaml.Behaviors.Wpf` and `System.Windows.Extensions`. I have tried the following troubleshooting steps: 1. Cleaned and rebuilt the solution multiple times. 2. Deleted the `.vs`, `bin`, and `obj` folders to force a fresh build. 3. Checked my project properties to ensure the startup project is set correctly. 4. Verified that no other instances of the application are running in the background. 5. Reset the Visual Studio settings to defaults. Here's a snippet of my `MainWindow.xaml.cs` where I'm initializing the application: ```csharp public partial class MainWindow : Window { public MainWindow() { InitializeComponent(); // Some initialization logic } } ``` When I try to debug, the output window doesn’t provide much useful information beyond the behavior. I also checked the Event Viewer, and I see a few entries related to .NET Runtime errors but nothing specific that points to the cause. Has anyone else encountered this scenario? Is there a specific configuration or setting in Visual Studio that I might be missing, especially after updating those packages? Any help would be greatly appreciated! For context: I'm using C# on Ubuntu. Any help would be greatly appreciated! This is for a REST API running on macOS. Any feedback is welcome! I recently upgraded to C# 3.10. Could someone point me to the right documentation? Is there a simpler solution I'm overlooking? This issue appeared after updating to C# latest. Any ideas what could be causing this? What are your experiences with this?