I've been having a real struggle trying to set up a demo application in Visual Studio 2015 using Asp.NET Core RC2 and Angular2 RC4. My package.json file (the one npm uses) was only picking up the Angular2 beta releases. 
I finally found the solution at https://github.com/angular/angular/blob/master/CHANGELOG.md in the section for 2.0.0-rc.0. Open a command window and change directory to the root directory of the solution (i.e. \<solution name>\src\<project name). Then run the command:
 npm install --save @angular/core @angular/compiler @angular/common @angular/platform-browser @angular/platform-browser-dynamic rxjs@5.0.0-beta.6 zone.js@0.6.12.
The dependencies section of my package.json file automagically updated to 
"dependencies": {
    "@angular/common": "^2.0.0-rc.4",
    "@angular/compiler": "^2.0.0-rc.4",
    "@angular/core": "^2.0.0-rc.4",
    "@angular/platform-browser": "^2.0.0-rc.4",
    "@angular/platform-browser-dynamic": "^2.0.0-rc.4",
    "es6-promise": "3.2.1",
    "es6-shim": "0.35.1",
    "reflect-metadata": "0.1.3",
    "rxjs": "^5.0.0-beta.6",
    "systemjs": "0.19.31",
    "zone.js": "^0.6.12"
  },

Finally the solution builds. Now to get it to do something useful...

Comments

Post a Comment

Popular posts from this blog

Debugging Unit Tests

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...
Read more

Visual Studio keyboard shortcuts

A few handy Visual Studio shortcuts and options: Ctrl + -/+ : Move backwards/forwards through navigation history. Ctrl + Alt + L : Shifts the focus to Solution Explorer. Start typing an items name to navigate to it. Ctrl + ; : Search Solution Explorer for a file. Ctrl + q : Search for menu items. To change vertical scroll bar to map mode: Tools > Options > Text Editor > All languages > Scroll Bars > User map mode for vertical scroll bar. To quickly view a file: Single click it in Solution Explorer or select it with the keyboard. When the focus is in the code editor: Alt + vertical arrow keys : Moves current line up or down. To move several lines, select them then Alt + vertical arrow keys.
Read more

Problem deleting directories and files in Windows

I was trying to delete a folder containing some node modules that was extremely deeply nested and kept getting errors to do with the file path being too long when using the standard File Explorer delete tools.  I eventually found a solution at  http://stackoverflow.com/questions/28175200/unable-to-delete-node-modules-folder . Create an empty folder somewhere, e.g. C:\test. Open up a command window and run the command 'robocopy /MIR c:\test <directory to delete>. The directory will now be empty and can itself be deleted. The /MIR switch makes robocopy copy the contents for the source directory (the empty one in this case) to the destination folder and delete any existing directories and folders in it.
Read more