Answer from StackOveflow that worked for me: If you are running into this error message can you please try adding the “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows Kits\Installed Roots\KitsRoot” registry key and give it the same value as "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Kits\Installed Roots\KitsRoot"
To enable debugging and stepping through unit test code when using NUnit: In the project containing the unit tests add a reference to nunit-console-runner.dll. Add a file to the project called NUnitConsoleRunner, for example. using System; using System.Collections.Generic; using System.Linq; using System.Text; namespace Utilities_Tests { public class NUnitConsoleRunner { [STAThread] public static void Main(string[] args) { NUnit.ConsoleRunner.Runner.Main(args); } } } Under the properties for the project: - Application - set the output type to Windows Application. - Debug - set the command line arguments to the name of the executable produced, e.g. Utilities_Tests.exe, and set the working directory to where it lives. Set the project to be the st...
I followed the installation instructions for node-sass but it would not run from the terminal. The message was something like 'command not found'. Eventually I worked out that I needed to add /Users/my_user_name/node_modules/node-sass/bin to the path. To do that see my post on setting the path on macs .
Comments
Post a Comment