You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Microsoft Visual Studio Community 2022
Version 17.4.2
VisualStudio.17.Release/17.4.3+33205.214
Microsoft .NET Framework
Version 4.8.04084
Installed Version: Community
Visual C++ 2022 00482-90000-00000-AA356
Microsoft Visual C++ 2022
ASP.NET and Web Tools 17.4.326.54890
ASP.NET and Web Tools
Azure App Service Tools v3.0.0 17.4.326.54890
Azure App Service Tools v3.0.0
C# Tools 4.4.0-6.22565.8+53091686b435746d62a5df56abfab0e71203d83a
C# components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.
Microsoft JVM Debugger 1.0
Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines
NuGet Package Manager 6.4.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit https://docs.nuget.org/
Syntax Visualizer 1.0
An extension for visualizing Roslyn SyntaxTrees.
TGit 1.0
Control TortoiseGit from within Visual Studio
Visual Basic Tools 4.4.0-6.22565.8+53091686b435746d62a5df56abfab0e71203d83a
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.4.0-beta.22512.4+525d5109e389341bb90b144c24e2ad1ceec91e7b
Microsoft Visual F# Tools
Visual Studio IntelliCode 2.2
AI-assisted development for Visual Studio.
Description
The manifest file does not open with VSIX-Manifest-Editor.
Probably it is my fold, probably not. I have no clue.
I hope someone can help.
Steps to recreate
Open solution MockLanguage.sln (github-version from Jan 7 23)
In solution explorer, project MockLanguageExtension double-click on source.extension.vsixmanifest
File is opened in with xml-viewer
In solution explorer, project MockLanguageExtension right-click on source.extension.vsixmanifest
Select "Open with" and VSIX-Manifest-Editor
Message box appears that says "The file cannot be opened with the selected editor. Please choose another editor."
Expected behavior
It should open the manifest with the manifest editor at the first place and without complaining.
A least it should give a hint what 's actually wrong.
The text was updated successfully, but these errors were encountered:
Installed products
Microsoft Visual Studio Community 2022
Version 17.4.2
VisualStudio.17.Release/17.4.3+33205.214
Microsoft .NET Framework
Version 4.8.04084
Installed Version: Community
Visual C++ 2022 00482-90000-00000-AA356
Microsoft Visual C++ 2022
ASP.NET and Web Tools 17.4.326.54890
ASP.NET and Web Tools
Azure App Service Tools v3.0.0 17.4.326.54890
Azure App Service Tools v3.0.0
C# Tools 4.4.0-6.22565.8+53091686b435746d62a5df56abfab0e71203d83a
C# components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.
Microsoft JVM Debugger 1.0
Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines
NuGet Package Manager 6.4.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit https://docs.nuget.org/
Syntax Visualizer 1.0
An extension for visualizing Roslyn SyntaxTrees.
TGit 1.0
Control TortoiseGit from within Visual Studio
Visual Basic Tools 4.4.0-6.22565.8+53091686b435746d62a5df56abfab0e71203d83a
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.4.0-beta.22512.4+525d5109e389341bb90b144c24e2ad1ceec91e7b
Microsoft Visual F# Tools
Visual Studio IntelliCode 2.2
AI-assisted development for Visual Studio.
Description
The manifest file does not open with VSIX-Manifest-Editor.
Probably it is my fold, probably not. I have no clue.
I hope someone can help.
Steps to recreate
Expected behavior
It should open the manifest with the manifest editor at the first place and without complaining.
A least it should give a hint what 's actually wrong.
The text was updated successfully, but these errors were encountered: