I have been using Compass to compile sass files in Windows environment either on a command line or using Compass-app to watch a directory.
I've just started using Visual Studio (pro 2013). I have installed sassy studio using nuget but I can not find any instructions as to how to compile.
It looks like sasssy studio comes with its own sass compiler or it can use Compass. I've looked at the setting menu but nothing seems obvious as to how to compile to CSS automatically on save or even doing it manually.
1) Does the set up require a config.rb file or is there a different way to set up the configuration (such as 'require' options)?
2) How does one initiate the compile operation either automatically or manually?
TIA
I had the same trouble, so I followed this guide for Integrating the Compass CSS Framework into Visual Studio. I installed Ruby and Compass and then added the path to the Ruby folder in the SassyStudio options.
I was originally using Web Workbench so my Visual Studio project was already set up as a Compass project (had a config.rb file). So now it compiles correctly when I save.
I don't know whether this is necessarily the correct way, but it worked for me.
Related
I am attempting to compile a .cpp file on Visual Studio 2019 Preview 1 and the file windows.h is not present on the system. What do I have to do to make this file available to Visual Studio? The file being compiled contains include <windows.h>.
windows.h usually comes from Windows SDK installation. Like you discovered, some projects might even require a certain version of Windows SDK. Therefore, when such compilation errors happen, the first thing to do is to read carefully the source code documentation, which might indicate what is needed to install in advance.
Visual Studio 2017/2019 become more modular than previous releases, so missing a component is expected, and you can always go back to VS installer to find the suitable components to install.
I'm currently part of a team that is working on a rather large Typescript project in Visual Studio. As time has gone by and different versions of the project has been released, we've run into a snag when it comes to the versioning of Typescript installed together with Visual Studio.
Scenario:
v 1.1.0 of product released, built on TypeScript 1.8
v 1.2.0 of product released, built on TypeScript 2.1
A bug from customer X is reported for the 1.1.0 version, and the team will start working on a fix.
Problem:
Visual Studio is currently configured to use the latest version of TypeScript (2.1 in this case), so the code from v 1.1.0 does not compile.
Yes, I can manually change typescript versions in the project file and move around on tsc.exe to make this work. Typescript is installed globally as well, but for some reason, they decided that Visual Studio will install the compiler in its own folder instead of acessing the globally installed one.
Hoping someone else has run into this problem, and have a better approach to this.
This was solved by adding the following parameter to my .csproj file:
<TypeScriptCompileBlocked>True</TypeScriptCompiledBlocked>
Ended up running a grunt watch task, using the globally installed TypeScript compiler to compile the project.
Fetched from the official TypeScript docs
If you are using a different build tool to build your project (e.g. gulp, grunt , etc.) and VS for the development and debugging experience, set true in your project. This should give you all the editing support, but not the build when you hit F5.
I am using sass (.scss) in Visual Studio 2015 with Web compiler.
It is working great as expected.
But the only problem is I am not able to see the file name in developer mode as it shows in Koala
To dubug, I feel this option will be really helpful
Can anybody suggest how can I enable the same in VS 2015 please?
I asume that you want to enable the sourceMap.
In order to do this, open the "compilerconfig.json.defaults" file that Web compiler automatically added to your project, and under sass, change the sourceMap to "true". This will turn on source mapping for all sass files. You can do this file by file basis as well (from compilerconfig.json) but i do not remember what exactly you needed to add there.
Following the instructions here,
I've installed prerequisites, downloaded the source for version 3.9 and had CMake generate LLVM.sln. Building the full solution takes some times, but seems to do what it's supposed to do.
When looking at get_library in bindings/python/llvm/common.py, the Python binding makes use of a file named "LLVM-<current version>.dll" but I can't find any "LLVM-3.9.dll" in the generated files.
How do I build LLVM-3.9.dll from source with Visual Studio?
You can check out my repository which is based on CRoger instructions and simply build the project LLVM.vcxproj in Visual Studio.
I'm working on an angular2#beta project in VS 2013 after familiarizing myself with it in IntelliJ. IntelliJ can be set to find the tsconfig.json file and, as of TypeScript 1.6, it can therefore read the "exclude" property and not attempt to compile any of the node_modules. Now that I've moved to VS 2013 with TypeScript 1.7, I'm running into the issue where it's trying to compile the node_modules. I've included the tsconfig.json, but from what I've read, tsconfig.json is fully supported only in VS 2015. Is that the latest on this issue? Is there some way to tell VS 2013 to exclude those files or to use my tsconfig.json instead?
I should also note that angular2#beta includes its typings with the rest of its source when I do an npm install. This puts all the typings mixed in with all the files, and I assume perhaps I could have to delete all the non-.d.ts files to get the typings without all the other errors. Previously you could use "tsd install angular2" to get the typings but this is no longer available. A solution to this would negate the previous problem.
Update
I can get all this working on VS 2015 - Community Edition, but I would really like to see if I can get it working on VS 2013.
Higher versions of Typescript will not be supported in Visual Studio 2013. But you don't need to edit and compile typescript files in one and the same IDE. It's handy but I use often different IDE's for the same project as long as the build processes are aligned (read: can be done by CLI). So yo can use Visual Studio Code for your Typescript work and compile it. Full support and Intellisense for the tsconfig file.
https://code.visualstudio.com/