VISUAL STUDIO INFORMATION

Microsoft Visual Studio Community 2022
Version 17.9.1
VisualStudio.17.Release/17.9.1+34616.47
Microsoft .NET Framework
Version 4.8.09037

Installed Version: Community

ASP.NET and Web Tools   17.9.195.45391
ASP.NET and Web Tools

Azure App Service Tools v3.0.0   17.9.195.45391
Azure App Service Tools v3.0.0

C# Tools   4.9.0-3.24081.11+989117396f26e5453ff157df610d22ce45b6b0a9
C# components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.

Extensibility Message Bus   1.4.39 (main@e8108eb)
Provides common messaging-based MEF services for loosely coupled Visual Studio extension components communication and integration.

Microsoft JVM Debugger   1.0
Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines

Mono Debugging for Visual Studio   17.9.0 (b3bca6f)
Support for debugging Mono processes with Visual Studio.

NuGet Package Manager   6.9.1
NuGet Package Manager in Visual Studio. For more information about NuGet, visit https://docs.nuget.org/

Razor (ASP.NET Core)   17.9.2.2408002+5aec2f1744a2273d3e7157cc4cc1986f87f524d4
Provides languages services for ASP.NET Core Razor.

TypeScript Tools   17.0.30103.2001
TypeScript Tools for Microsoft Visual Studio

Visual Basic Tools   4.9.0-3.24081.11+989117396f26e5453ff157df610d22ce45b6b0a9
Visual Basic components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.

Visual F# Tools   17.9.0-beta.23614.3+a521e1cd420beb56c15faf6836184fadd2b7937a
Microsoft Visual F# Tools

Visual Studio IntelliCode   2.2
AI-assisted development for Visual Studio.

VisualStudio.DeviceLog   1.0
Information about my package

VisualStudio.Mac   1.0
Mac Extension for Visual Studio

VSPackage Extension   1.0
VSPackage Visual Studio Extension Detailed Info

Xamarin   17.9.0.138 (d17-9@60c2b9b)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

Xamarin Designer   17.9.3.0 (remotes/origin/d17-9@f174974f91)
Visual Studio extension to enable Xamarin Designer tools in Visual Studio.

Xamarin Templates   17.9.0 (38e87ba)
Templates for building iOS, Android, and Windows apps with Xamarin and Xamarin.Forms.

Xamarin.Android SDK   13.2.2.0 (d17-5/45b0e14)
Xamarin.Android Reference Assemblies and MSBuild support.
    Mono: d9a6e87
    Java.Interop: xamarin/java.interop/d17-5@149d70fe
    SQLite: xamarin/sqlite/3.40.1@68c69d8
    Xamarin.Android Tools: xamarin/xamarin-android-tools/d17-5@ca1552d


Xamarin.iOS and Xamarin.Mac SDK   16.4.0.23 (9defd91b3)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.
        

UPGRADING VISUAL STUDIO

Upgrading Visual Studio to a more recent version is usually a smooth process, but now and then, it goes awry. Hopefully, if you find yourself in the following situation, this information will prove helpful.

When you use the Help => Check For Updates menu option from inside Visual Studio, it launches the Visual Studio Installer, which is supposed to kill off all running devenv.exe processes before proceeding to upgrade. Unfortunately, it seems like sometimes it doesn't. For this reason, you should avoid upgrading from within Visual Studio; instead, use Task Manager to ensure no devenv.exe processes are running, then run the Visual Studio Installer directly from the Windows Start Menu. It should minimize the chance of problematic upgrades.

If you have a problem upgrading, you may see warning message boxes pop up when loading the Eamon CS solutions. They read (in part):

The XYZ package did not load correctly.

Where XYZ is a package name that varies. The solution to this problem is simple, purge the contents of Visual Studio's component cache:

1. Open an Administrator Command Prompt
2. CD %localappdata%\Microsoft\VisualStudio\17.0_*\ComponentModelCache
3. Verify you are in the ComponentModelCache directory before proceeding to delete its contents
4. DEL /F /Q *

Note: the directory 17.0_* corresponds to the version number for Visual Studio 2022; other Visual Studios will differ.

The next time an Eamon CS solution opens in Visual Studio, it will rebuild the cache, and everything should work as expected.