When publishing to Windows Azure, you may get the warning WAT150:
warning WAT150: The project ‘MyProject’ is dependent on the following assembly: J:\Sources\MyProject\packages\Microsoft.Data.Services.Client.5.6.0\lib\net40\Microsoft.Data.Services.Client.dll. This assembly is not in the package. To make sure that the role starts, add this assembly as a reference to the project and set the Copy Local property to true.
This warnings means that one of your projects uses an assembly that’s installed locally on your computer (e.g. using ASP.NET in a worker role) but is not installed on the Azure instance you want to run the package on. So, usually you can’t ignore this warning as the resulting package won’t run.
The usual fix is to use Nuget packages instead of globally installed assemblies. However, if this doesn’t work (like in my example above where the package clearly comes from Nuget), there’s another culprit:
The Global Assembly Cache (GAC)
Basically, if the referenced assembly is registered in the GAC with exactly the same version, then Visual Studio will always use the assembly from the GAC. Because of this, the assembly won’t be copied to the output directory and thus won’t be in the Azure package – resulting in WAT150 warnings.
This seems to be like this by design. Quoting from MSDN:
If you deploy an application that contains a reference to a custom component that is registered in the GAC, the component will not be deployed with the application, regardless of the CopyLocal setting. In previous versions of Visual Studio, you could set the CopyLocal property on a reference to ensure that the assembly was deployed. Now, you must manually add the assembly to the \Bin folder. This puts all custom code under scrutiny, reducing the risk of publishing custom code with which you are not familiar.
This statements is not entirely correct. Setting CopyLocal to true works – but only for the project directly referencing the assembly. Unfortunately, CopyLocal is not transitive, i.e. if
project A references assembly
X.dll (registered in the GAC; with CopyLocal set to true) and
project B references
project A, then
X.dll will only appear in the output directory of
project A but not in the output directory of
project B. (It would appear in the output directory of
project B if
X.dll wasn’t in the GAC.)
How to fix ∞
There are a couple of ways how to fix this problem, but they all are workarounds:
- Delete the assembly from the GAC: Navigate to
%WINDIR%\Microsoft.NET\assembly\GAC_MSILand delete the assembly from here. Note though that these assemblies may still be need and some software may stop working.
- Switch to a different assembly version that’s not in the GAC.
- Reference the necessary assemblies directly in all role projects.