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.
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.
So I would like to use my Macbook to build a new app but the tools I typically use for SASS, mainly the Web Compiler extension, are not supported on Mac. Is there a similar tool I can use on Mac in VS to compile Sass?
I'm using Visual Studio 2019 for Mac, Community Edition.
Looking at the Web Compiler extension it seems to use node-sass to compile the .sass files.
If you can get that working on the command line then you could do one of the following:
Run that command from the Terminal window.
Add a post or pre-build step to the project which runs that command.
Look at installing the BuildWebCompiler NuGet package which looks to be used by the Web Compiler extension to enable files to be generated on build.
Install the Task Runner Explorer extension and setup a package.json with a command that will run node-sass. Then the NPM task runner should be able to detect that and run it.
I installed Visual Studio 2015 and TypeScript 1.8.6 for Visual Studio 2015. After creating a new TypeScript project and building, I get this build error:
No compiler was found at C:\Program Files (x86)\Microsoft
SDKs\TypeScript\1.8\tsc.exe
Indeed, tsc.exe is missing in the file system.
Things I've tried:
Uninstall and re-install TypeScript Tools for Visual Studio 2015 1.8.6.0
Uninstall and re-install TypeScript Tools for Visual Studio 2013 1.8.5.0
Repair TypeScript Tools for Visual Studio 2015 1.8.6.0
I HAVE tried turning it off and on again :-)
Any clue on how to solve this? Which component installs the TypeScript SDK?
MSBuild is looking in the wrong place for tsc.exe
It should be looking in 'C:\Program Files (x86)\Microsoft SDKs\TypeScript\ tsc version \tsc.exe'
e.g. C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.8\tsc.exe
The one thing the TypeScript SDK installer wont do, is upgrade your existing projects. So all that reinstalling wont change anything. However, if you want MSBuild to use the newer compiler, you can upgrade your project yourself.
I don't think there is any way to do this through the UI, but it's easy enough to edit the Project file.
It needs to contain this in the first PropertyGroup
<TypeScriptToolsVersion>1.7</TypeScriptToolsVersion>
If you want the build to use v1.8.6, you need to set
<TypeScriptToolsVersion>1.8</TypeScriptToolsVersion>
In your case, I'm betting it's not there at all. So you should just add it.
I'm not experienced with using the TypeScript tools for Microsoft.. what you could do is use Gulp or Grunt tasks to compile TypeScript, this will even allow you to compile the TypeScript files everytime your save your .ts files.
You will need NPM (Node Package Manager) to install Gulp or Grunt and then install the package for compiling TypeScript.
You can find some information about the Grunt TypeScript package here: https://www.npmjs.com/package/grunt-typescript
Or for information about the Gulp TypeScript package, check this: https://www.npmjs.com/package/gulp-typescript
I've read through the comments on this issue on the TypeScript Github repo. Although this is a different issue, I did find a clue: repairing Visual Studio 2015 (through the Control Panel) installed tsc.exe in the correct folder.
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.