Hi, thanks for your response. I had assumed that it was NuGet since the issue occurred only when using the package management interface. However, after much testing with clean solutions I believe that it is another VS plugin causing this. My apologies for reporting it here in error.
Thanks again.
Thanks again.