I'm editing an existing Sass project, in the mixin.scss file I find the following:
//elements get appended with "__" and the $name
#mixin e($name) {
#at-root &__#{$name} {
#content;
}
}
That seems correct to me, but Visual Studio 2013 intellisense and compiler gives me an error:
"at-root is not a valid # directive"
Visual Studio Web Essentials uses libsass to compile SASS files to CSS. Unfortunately libsass does not yet support version 3.3 which is when #at-root was introduced.
See this GitHub issue for more info.
Related
I have a number of import statements at the top of the SCSS file in a project I've inherited. Here are the relevant statements:
...
#import "node_modules/bulma/bulma.sass";
...
#import "node_modules/buefy/src/scss/buefy.scss";
...
Using Webcompiler, the SCSS file compiles in Visual Studio 2019. However, when I try to compile it in Visual Studio 2022 I get an error saying it can't find the bulma stylesheet. I tried adding "node_modules" to the includePath in the SASS section of compilerconfig.json.defaults. This seemed to work for the bulma stylesheet but I then got that same error on the buefy stylesheet. The files are definitely present (otherwise it wouldn't compile in VS2019).
Anyone any ideas? Is there a setting in Visual Studio 2022 that I'm missing?
Thanks
the extension webcompiler does not work with visual studio 2022 (not sure if it will be fixed)
Someone ported the extensions to VS2022
Note: I'm not the author of the port, or of the original extensions.
I tried to setup SDL 2 in visual studio following similar instruction to tutorial and the result was that visual studio was recognizing SDL.h but it was not recognizing SDL2/SDL.h and the include folder of sld2 development tools (link) does not have any SDL2/SDL.h file. How to setup SDL2/SDL.h in visual studio ?
Actually SDL2 in SDL2/SDL.h is a folder.It is a folder that keeps SDL.h in the directory the compiler looks #include directives in.Change that include folder name to SDL2.
I can build my Q# projects fine, but VS 2017 (v. 15.9.4) has the Intellisense errors code QS6103 of "No namespace with that name exists." for my first two "open" statements shown below. I have tried with both the "0.3.1811.1501" and "0.3.1811.2802" versions of the SDK and Canon.
namespace Quantum.QSharpApplication1
{
open Microsoft.Quantum.Primitive;
open Microsoft.Quantum.Canon;
operation HelloQ () : Unit {
Message("Hello quantum world!");
}
}
What version of .NET Core do you have installed? (You can check using dotnet --version)
I ran into similar problems with Q# IntelliSense not recognizing library namespaces, with .NET Core 2.1.500 and 2.1.403, but with 2.1.402 it works fine. I had to uninstall the higher versions though.
I installed SASS on visual studio code, but only works with the scss syntax.
file.scss are not recognized by the VS code ( when I use the classic indented syntax of sass).
Is there something in the gulpfile.js that i have to change?
You'll need an extension that handles .sass files, like
Sass extension from vscode marketplace
They are others as well.
I am trying to compile the SCSS files in a projetc using Visual Studio 2013 and Web Essentials. Here is the error I am getting in the visual studio output window is
Something went wrong reaching: http://127.0.0.1:52658/?service=SCSS&sourceFileName=C:\Development\KnockApp\KnockApp\KnockApp.Web\Content\scss\directory.scss&targetFileName=C:\Users\IEUser\AppData\Local\Temp\3510b388-06aa-48bb-b517-e1442399e924.css&mapFileName=C:\Users\IEUser\AppData\Local\Temp\3510b388-06aa-48bb-b517-e1442399e924.css.map&precision=5&outputStyle=expanded&
SCSS: directory.scss compilation failed: The service failed to respond to this request
Possible cause: Syntax Error!
The SCSS files come from a third party theme and they use Compass, I have included the compass files in my project. I also have node and node-sass installed on the machine.
Any thoughts?
Got same error and found solution.
Web Essentials uses node.exe to build SCSS, but this service is crashed when tried to compile some partial SCSS with unresolved dependencies.
After that Visual Studio logs 'Something went wrong reaching' messages on each build, to fix this error just kill all 'node.exe' processes and build main SCSS file again.