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
This extension: 1.12.405 Or should I use Web Compiler 2022 fork?
Description
I'm expecting option for Web Compiler on scss file context menu, but it is not there. I see no other options elsewhere.
Steps to recreate
Used NuGet in VS 2022 to install BuildWebCompiler
No errors on installation, NuGet installation shows it as installed on my project
Extension does not show on Extension manager.
Have Bootstrap and its Bootstrap.SASS
Have a custom .scss importing Bootstrap and containing some custom mods.
The project is an ASP .Net Web Forms project. Is the extension limited to certain kinds of projects? Does it depend on existence of a project file?
Any help appreciated.
The text was updated successfully, but these errors were encountered:
itorres008
changed the title
Don't get Web Compiler option on context menu. Unsure is BuildWebCompiler is same as WebBuilder
Don't get Web Compiler option on context menu
Sep 8, 2023
You're in luck. I solved this using Visual Studio Marketplace .vsix Installer
This version was discontinued and forked into a WebCompiler 2022. I solved this using its Visual Studio Marketplace .vsix Installer
Process here: failwyn#88
Installed product versions
Description
I'm expecting option for Web Compiler on scss file context menu, but it is not there. I see no other options elsewhere.
Steps to recreate
Used NuGet in VS 2022 to install BuildWebCompiler
No errors on installation, NuGet installation shows it as installed on my project
Extension does not show on Extension manager.
Have Bootstrap and its Bootstrap.SASS
Have a custom .scss importing Bootstrap and containing some custom mods.
The project is an ASP .Net Web Forms project. Is the extension limited to certain kinds of projects? Does it depend on existence of a project file?
Any help appreciated.
The text was updated successfully, but these errors were encountered: