{ "id": "guide/visual-studio-2015", "title": "Using Angular with Visual Studio 2015", "contents": "\n\n\n
Some developers prefer Visual Studio as their Integrated Development Environment (IDE).
\nThis cookbook describes the steps required to set up and use Angular app files in Visual Studio 2015 within an ASP.NET 4.x project.
\nThere is no live example for this cookbook because it describes Visual Studio, not\nthe Angular application itself. It uses the starter Angular application created by the CLI command ng new
as an example.
To set up the Getting Started files with an ASP.NET 4.x project in\nVisual Studio 2015, follow these steps:
\nIf you prefer a File | New Project
experience and are using ASP.NET Core,\nthen consider the experimental\nASP.NET Core + Angular template for Visual Studio 2015.\nNote that the resulting code does not map to the docs. Adjust accordingly.
Install Node.js® and npm\nif they are not already on your machine.\nSee Local Environment Setup for supported versions and instructions.
\nThe minimum requirement for developing Angular applications with Visual Studio is Update 3.\nEarlier versions do not follow the best practices for developing applications with TypeScript.\nTo view your version of Visual Studio 2015, go to Help | About Visual Studio
.
If you don't have it, install Visual Studio 2015 Update 3.\nOr use Tools | Extensions and Updates
to update to Update 3 directly from Visual Studio 2015.
Configure Visual Studio to use the global external web tools instead of the tools that ship with Visual Studio:
\nTools
| Options
.Projects and Solutions
| External Web Tools
.$(PATH)
entry above the $(DevEnvDir
) entries. This tells Visual Studio to\nuse the external tools (such as npm) found in the global path before using its own version of the external tools.Visual Studio now looks first for external tools in the current workspace and\nif it doesn't find them, it looks in the global path. If Visual Studio doesn't\nfind them in either location, it will use its own versions of the tools.
\nWhile Visual Studio Update 3 ships with TypeScript support out of the box, it currently doesn’t ship with more recent versions of TypeScript, which you need to develop Angular applications.
\nTo install the latest version of TypeScript:
\nDownload and install the latest TypeScript for Visual Studio 2015,
\nOR install it with npm: npm install -g typescript@latest
.
You can find out more about TypeScript support in Visual Studio here.
\nAt this point, Visual Studio is ready. It’s a good idea to close Visual Studio and\nrestart it to make sure everything is clean.
\n Follow the instructions in Local Environment Setup to create a starter Angular app using the CLI command ng new
.
Create the ASP.NET 4.x project in the usual way as follows:
\nFile
| New
| Project
from the menu.Templates
| Visual C#
(or Visual Basic
) | Web
.ASP.NET Web Application
template, give the project a name, and click OK.This cookbook uses the Empty
template with no added folders,\nno authentication, and no hosting. Pick the template and options appropriate for your project.
Copy files from the starter Angular app into the folder containing the .csproj
file.\nInclude the files in the Visual Studio project as follows:
Click the Show All Files
button in Solution Explorer to reveal all of the hidden files in the project.
Right-click on each folder/file to be included in the project and select Include in Project
.\nMinimally, include the following folder/files:
Restore the packages required for an Angular application as follows:
\npackage.json
file in Solution Explorer and select Restore Packages
.\nnpm
to install all of the packages defined in the package.json
file.\nIt may take some time.View
| Output
) to watch the npm commands execute.Installing packages complete
. Be patient. This could take a while.Refresh
icon in Solution Explorer.node_modules
folder in the project. Let it be a hidden project folder.First, ensure that src/index.html
is set as the start page.\nRight-click index.html
in Solution Explorer and select option Set As Start Page
.
Most Visual Studio developers like to press the F5 key and see the IIS server come up.\nTo use the IIS server with the Getting Started app, you must make the following three changes.
\nindex.html
, change base href from <base href=\"/\">
to <base href=\"/src/\">
.index.html
, change the scripts to use /node_modules
with a slash\ninstead of node_modules
without the slash.src/systemjs.config.js
, near the top of the file,\nchange the npm path
to /node_modules/
with a slash.After these changes, npm start
no longer works.\nYou must choose to configure either for F5 with IIS or for npm start
with the lite-server.
If your app uses routing, you need to teach the server to always return\nindex.html
when the user asks for an HTML page\nfor reasons explained in the Deployment guide.
Everything seems fine while you move about within the app.\nBut you'll see the problem right away if you refresh the browser\nor paste a link to an app page (called a \"deep link\") into the browser address bar.
\nYou'll most likely get a 404 - Page Not Found response from the server\nfor any address other than /
or /index.html
.
You have to configure the server to return index.html
for requests to these \"unknown\" pages.\nThe lite-server
development server does out-of-the-box.\nIf you've switched over to F5 and IIS, you have to configure IIS to do it.\nThis section walks through the steps to adapt the Getting Started application.
Visual Studio ships with IIS Express, which has the rewrite module baked in.\nHowever, if you're using regular IIS you'll have to install the rewrite\nmodule.
\nTell Visual Studio how to handle requests for route app pages by adding these\nrewrite rules near the bottom of the web.config
:
The match url, <match url=\".*\" />
, will rewrite every request. You'll have to adjust this if\nyou want some requests to get through, such as web API requests.
The URL in <action type=\"Rewrite\" url=\"/src/\"/>
should\nmatch the base href in index.html
.
Build and launch the app with debugger by clicking the Run button or by pressing F5
.
It's faster to run without the debugger by pressing Ctrl-F5
.
The default browser opens and displays the Getting Started sample application.
\nTry editing any of the project files. Save and refresh the browser to\nsee the changes.
\n\n \n