ASP.NET Compilation and other files don't mix

First posted on: 2019/03/05

Last modified: 2019/07/11,6a40e30

Categories: infrastructure

I love working in software. Mostly things work as expected, but at times no. I changed A, how can Z be affected - after all they are all miles apart. Right? Wrong. Z can be affected. Today’s story is the latest - totally unexpected, but not surprising.

Background

We run ASP.NET compilation on our code base as part of every build in our Continuous Integration (CI) pipeline. I changed some part of the pipeline so that we started caching node_modules directory between different parts of a pipeline. So basically, .NET project A which did not have node_modules directory when ASP.NET compilation was being run earlier now has a node_modules directory.

Issue

The ASP.NET compilation was failing with an error:

Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" could not be located.

Searching for it, I come across this StackOverflow post. The issue is that the ASP.NET compiler was trying to compile the JavaScript files as well.

Solution

This is a hack, not a solution. I removed the node_modules directory before running the ASP.NET compilation.