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

Path environmental variable on mac

To view your paths in terminal type: $ echo $PATH To add a path for the duration of this terminal session type: $ export PATH=$PATH:/my/new/path Note: the $PATH: is important as it adds the new path to your existing one. Without $PATH: the existing path is overwritten with the new one. The disadvantage with this approach is that you modification to the path is lost when the terminal session ends. To add to the path for all users permanently you need to edit the paths file in /etc.  In terminal navigate to /etc. Type $ sudo pico paths Add your path. Type ^x (note: ^ = ctrl key). You'll be prompted to save. Type Y . To view your paths using echo $PATH you'll need to reopen the terminal to see your changes.
Read more

Setting up node-sass on a mac

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