Comments on: Running Multiple Websites in a Windows Azure Web Role

By: Derek Hamilton

Derek Hamilton — Mon, 28 Jan 2013 13:07:00 +0000

Is this considered valid?

…

By: Tips for Publishing Multiple Sites in a Web Role « Michael S. Collier's Blog

Mon, 14 Jan 2013 14:01:37 +0000

[...] Wade Wegner’s blog post - http://www.wadewegner.com/2011/02/running-multiple-websites-in-a-windows-azure-web-role/ [...]

By: jashoe

jashoe — Thu, 16 Aug 2012 22:39:49 +0000

Have you ever tried this with WCF rather than web sites?
*) Create a WCF Service Web Role project
*) Add a second site with a VirtualApplication tag that points to a directory containing a WCF service that was published to the file system
I have tried this with the emulator and it seems to work fine. When I publish to Azure it seems to be confused by the multiple sites. It throws an exception on deploy trying to access e:\sitesroot\2 – but there is no such directory, the sites folders are 1 and 3.

I am trying to create a solution that pulls WCF services into an Azure package and allows me to use the VirtualDirectory and VirtualApplication tags to build up URLs to access the services.

By: Jose

Jose — Mon, 23 Jul 2012 19:58:30 +0000

Hello:
One question, is necesary put togheter in one same solution all webSites?
but need host some projects webSites in one Azure Web Role, but can’t join all in one solution.
It is possible.

Regards

By: Multiple applications per web role | PHP Developer Resource

Multiple applications per web role | PHP Developer Resource — Thu, 24 May 2012 00:51:30 +0000

[...] Running Multiple Websites in a Windows Azure Web Role [...]

By: MattD

MattD — Wed, 09 May 2012 09:00:15 +0000

Excellent Joe!!!! Works a dream!

Although you may need to add the parameter /p:AutoParameterizationWebConfigConnectionStrings=False to the msbuild line to stop it from parameterising your data connections … that or workout a strategy to manage parameterisation properly;)!

By: tugberk

tugberk — Wed, 01 Feb 2012 15:19:44 +0000

Thanks for this great post.

What I am wondering is that how I should configure my dns records. Let’s take your first multiple app sample and we would be running two sites under one role.

In that case, what would be the dns record of http://www.litware.com? I went through the smarx’s blog post about that but I would like to know if I should take any additional step if I use multiple sites under one role.

By: Jim

Jim — Wed, 01 Feb 2012 00:40:53 +0000

Thanks for the article – but I am confused with “Hit F5 and take a look at IIS” Not sure where to see the IIS. Is this the same as CONTROL PANEL –> ADMINISTRATIVE TOOLS –> IIS?

By: Joe

Joe — Sat, 24 Dec 2011 11:31:39 +0000

This post is getting a bit long in the tooth, but I did find a way to automate this, so I thought I’d share it for anyone who happens to google their way here. Doing a manual file system publish of each site before creating the Azure package (as Bugeo suggests) can quickly become unmanageable when running a lot of sites in a single role. This is especially true if you’re working in a team environment where you might not be the only person making updates to the websites.

These instructions assume:
1) The Azure project and the website projects are in the same solution
2) The Azure project is named “MyAzureProject”
3) The website projects live alongside the Azure project in the file system hierarchy

For example:

MySolution
|- MyAzureProject
|- Website1
|- …
|- WebsiteN

1) For each website included in the role, right-click the project and choose Properties. On the Build Events page, set the following values.

Pre-Build Command Line:
rmdir “$(ProjectDir)..\MyAzureProject\Sites\$(ProjectName)” /S /Q

Post-Build Command Line:
%WinDir%\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe “$(ProjectPath)” /T:PipelinePreDeployCopyAllFilesToOneFolder /P:Configuration=$(ConfigurationName);PreBuildEvent=”";PostBuildEvent=”";PackageAsSingleFile=false;_PackageTempDir=”$(ProjectDir)..\MyAzureProject\Sites\$(ProjectName)”

The post-build command will do a local file system publish of the website into the MyAzureProject\Sites\WebsiteProjectName directory each time you build. The pre-build command ensures that you don’t accidentally have stale outputs should the website project not build correctly.

2) Right-click the Azure project and choose Project Dependencies. Make sure all of the website projects are selected. This will ensure that the website projects are always built (and published locally) before creating the Azure deployment package.

3) Edit the ServiceDefinition.csdef file as Wade describes in the section “Run Two Different Projects in the Web Role.” The value for each physicalDirectory attribute should be “Sites\WebsiteProjectName” – which is the local publish destination we specified for the website project in step 1.

Now when you publish your Azure package from MyAzureProject, all the included sites will auto-magically build and publish themselves, and all necessary files (and nothing more) will be included in the package. Additionally, if any included website fails to build, then the package creation will also fail (rather than silently “succeeding” and creating a package with missing or stale outputs).

By: Mark

Mark — Mon, 14 Nov 2011 05:46:46 +0000

Its nice one. Actually I am working in 1 Winzaure cloud project. I need your assistance guidance in it.
First question, I configured all necessary property for symbolic link at cloud. Still its not working well. I’m using PHP 5.3.6 Version. Can u guide me. how I can enable symbolic link.
Second question . When we upload/create cloud. We get administrator or guest environment.

I tested my code on Window Server 2008. Its working well there but not in cloud.
Thanks
Mark