Azure package not including linked project DLL even with copy local set

Question

I've an Azure solution with 4 projects in it. (VS 2012 on Windows 8, Azure Tools 1.8)

1. Core project with common code
2. Web Role Front End
3. Service Role for servicing data (from SQL Azure DB)
4. Worker Role for scheduled tasks

All role projects have a reference to the core project with copy local = true... standard stuff.

The web role and the worker role work fine, but my service role keeps getting stuck in the Initializing - Starting - Recycling loop. When I browse to the service I get the Could note load file or assembly FileNotFoundException. Sure enough, RDP to the server and the DLL is missing.

Having a look in the package files locally, the other roles include the missing DLL, but not the service role.

If I use VS to publish the service role (not azure publish) to local file system, the core DLL is included, proving that the VS settings are correct for the copy local.

Is there any other way from within VS to influence the files that are added to the Azure deployment package, or is there a simple way to script the creation of the package without using VS?

Answer 1

As I wrote in comment I have same situation as you (Windows 7 and 8, VS 2012, Azure SDK 1.8). Copy Local is set to true but when I open *.cspkg package, referenced assemblies are missing in approot folder. What I did I created new Worker Role project and copied the code from old one. Now are all assemblies included.

UPDATE: The solution described above was not really necessary in my case. The real problem by me was that my Web Role accidentally referenced my Worker Role assembly. When I removed this unnecessary reference, the Worker Role got the all assemblies in package. This behaviour is, on my opinion, buggy.