OutputPath in a WebApi 2 project can mess with your Azure Compute Emulator

Long story short:
I had a non-default OutputPath set in my project’s properties, “\bin\Test” instead of just “\bin”. This caused all sorts of errors where the Azure emulator (which used IIS Express by the way) didn’t pick up changes in my code. I found out after deleting all bin folders AND at the same time adjust my OutputPath for the project.

This is actually the second “gotcha” of the day with the OutputPath. The other was that <PropertyGroup> in your .csproj file must be defined above any <Import> statements that are used during building. See this StackOverflow answer.

Who knew?!