Skip to main content

Process with an ID #### is not running on Visual Studio 2015 – How to fix it

If you’re working with Visual Studio on recent Windows versions, such as Windows 10, you might stumble upon the following error when trying to open an ASP.NET Core or MVC solution:

Process with an ID #### is not running on Visual Studio 2015

If you look to the Visual Studio error log window panel, you should also see something like that:

This is clearly an IISExpress error. It’s worth noting that the solution will still be launched in debug mode, but the web browser will be unable to connect to the application, giving the following permanent error:

Unable to launch the IIS Express Web server.

The start URL specified is not valid. https://localhost:#####/

There are many workaround that might fix this issue: we suggest to try them one after another, stopping only when you manage to fix it.

Read More

Visual Studio 2015 – How to update NodeJS and/or NPM to their latest version

Among the things I love the most in Visual Studio 2015 is the seamless integrations of some of the most advanced community-driven, modern development tools such as Node.js, NPM and Bower. Conversely, among the things I love the least there is the fact that, sadly, the designers chose to ship the product with it’s own version of Node.js and NPM providing them in a internal bundle package instead of installing and using them as external executables. This can be a minor nuisance or a major problem, depending how much you’re using these tools and how often you need to keep them up-to-date – which is something that VS2015 doesn’t allow you to do from within the GUI.

Luckily enough, we can easily update them both with a bit of manual work: let’s see how.

Read More

Visual Studio 2015 – How to fix TypeScript TS2304 compilation errors (and other ES6 compiling/transpiling issues)

I recently had my hard time trying to setup an ASP.NET Core 1.0Angular2 RC1 Web Project with Visual Studio 2015 and make the embedded TypeScript compiler/transpiler accept it. These were the errors I was facing:

As far as I knew, the issue was indeed related to the recent upgrade I made switching Angular2 beta to Angular2 RC1. I managed to fix that, but it took a fair amount of time due to the lack of documentation almost anywhere. Since I feel like it can happen to other developers, I will share the workarounds I found hoping to help someone to waste less time than I had to.

Read More

Fixing TypeScript “Compile on Save” feature in Visual Studio 2015 ASP.NET 5 RC1

One day I’ll write an extensive post about TypeScript, the amazing JS superset developed by Microsoft in 2012 and now widely adopted by a bunch of good projects such as Angular 2, ngrx/store and SearchKit. If you stumbled upon this post you’re probably already using it and you’re fully aware of how it works. To put it in short terms:

  • You write your source code using TypeScript proprietary syntax.
  • Your code is compiled into plain JavaScript by a dedicated compiler (tsc) upon a trigger.
  • The trigger is raised upon each build or upon a file change, depending on your Visual Studio general and/or project-specific settings.

Needless to say, setting the compile trigger upon file change is something that will greatly benefit your development speed. In order to activate it, you basically have two options: modifying the Visual Studio general settings for non-project files, or alter your project-specific settings.

Read More