I have an Azure solution with 4 projects in it. (VS2012 on Windows 8, Azure Tools 1.8) 1 project is common logic that the other 3 projects all reference via a ProjectReference with copy local set to true.
When the Azure package is created, one of the role packages does not include the referenced assembly, while the other two do.
- Core project with common code
- Web Role Front End
- Service Role for servicing data (from SQL Azure DB)
- Worker Role for scheduled tasks
This results in the Web Role and Worker Roles functioning correctly, but the service role gets stuck in the Initializing - Starting - Recycling loop.
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 setting.
I have also tried the hack where you add the dll as a linked file content resource that copies to the project output, but that makes no difference, the dll is in the output when I build and run locally, it just doesn't get inserted into the package.
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?
FYI: .csproj, same in all projects. (except the core one)
<ItemGroup><ProjectReference Include="..\AzureDispatchCore\AzureDispatchCore.csproj"><Project>{89d912ec-68fc-4b40-b13f-51ea61a2318d}</Project><Name>AzureDispatchCore</Name></ProjectReference><ItemGroup>