The process of installing, configuring, and customizing Visual Studio to support development workflows across languages, platforms, and workloads.
Hello @RogerSchlueter-7899,
Could these solutions be built correctly before this issue appeared?
Is this issue replicated in a newly created VB project? If so, could you kindly share us the complete steps?
Currently, please try following(clean cache, repair VS and restore NuGet packages):
- Rename/Remove the hidden .vs folder in your solution folder, rebuild your solution/project.
- Repair VS from VS Installer => More => Repair(this takes some time).
- Open VS, click Tools => NuGet Package Manager => Package Manager Settings => check "Allow NuGet to download missing packages" and "Automatically check for missing packages during build in Visual Studio" options => click "Clear All NuGet Storage" => Right-click your solution => Restore NuGet Packages.
- In case the issue is caused by the namespace conflict, try to use the complete namespace, see if the error disappears(
Windows.Application=>System.Windows.Application).
Best Regards,
Tianyu
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.