I have a single web project that I want deploy in Azure.
I want to create one IIS web site per country and I want to be able to deploy each web site independently (not all of them at a time). How to do this?
Well,
you have two options:
Use Windows Azure WebSites to host your websites
Use Windows Azure Accelerator for WebRoles or your own project similar to that approach.
However you have to note that the second option is a project that is no longer being supported due to avialability of Azure Websites. With Azure Websites, you can have almost everything you get with the Accelerator. You can host your websites on a dedicated instances, and manage them individually. You can update/deploy your website data via FTP/GIT/TFS/WebDeploy, whichever method you are most happy with. The only downside of websites which I see, is the lack of Startup Tasks and the ability to customize your environment (Windows, IIS settings, etc).
When you have set up your Azure account you can go the the web sites section and start the construction of your Azure web spaces, the interface in the preview is very straight forward to use and intuitive.
For deployment using the publish command in from Visual Studio 2012 (which I found the easiest) here are the steps you will need to undertake:
For each of your countries you will need to set up the web site
in azure.
Then for each of those web sites you have created go
to their dashboard page and download the publish profile settings.
It is these settings that you can import into you Visual Studio
solution by selecting the publish command and browsing for the
settings profile file you downloaded and importing it.
Then in future when
you right click on the web site in your solution and select publish
it will publish to your web site in Azure.
I have created a fictional website for Spain below is the link you will need in order to initiate a publish from Visual Studio.
------------ EDIT -------------
For Visual Studio 2010 I met some difficulties trying to publish, in fact the publish profile you can download was not importable to Visual Studio 2010, well at least I could not figure it out.
Instead I created a deployment user by clicking on the 'Reset Deployment Credentials' link on the Azure dashboard (see the link in the image), created the user and then published via FTP from Visual Studio 2010.
What I would like to flag up is the maintenance issue of having one site for each country rather than one site with Localization, (if it is a language issue). A small change multiplied just 20 times for 20 different countries becomes a larger task and if you have lots of little changes it soon becomes a large task to maintain them all.
Related
I've recently built an ASP.NET website using C#.
Using the publishing wizard within Visual Studio 2013 I see that I can publish to "Microsoft Azure Websites", and I have done so. It worked great.
However, logging into the Azure account I'm not able to locate this website anywhere so that I may manage it directly, and see what the burn rate (costs) are.
Where are these "Microsoft Azure Websites" stored once they are published, within Azure?
Many thanks in advance.
Bob
Under Web Apps in the old portal and under App Services in the new one.
I'm running Visual Studio 2013 Premium and I've installed Microsoft Azure Tools for Microsoft Visual Studio 2013 v 2.5. I'm signed in with my Microsoft Account that also has admin permission in my Azure subscription.
The problem is that I can't see any web apps in the server explorer; I want to try remote debugging. I see a bunch of other Azure artifacts, but no web apps. Service bus and SQL databases lists content I expect. In screenshots I've seen on various MSDN posts, there should be a separate web apps node. I see an App Services node that doesn't list anything. All web apps are listed when I go to manage.windowsazure.com and portal.azure.com.
The App Service node has a context menu that allows me to create a new site. I did that and things got created correctly but nothing is displayed under the node.
This problem exists on both my home machine and work machine; both running a version of Windows 8.1. On my home machine I've re-installed the Azure tools without any effect.
I thought this too, for months. They renamed web sites to web apps, and are still seemingly renaming/moving things around. I just discovered my web site now live in Azure\App Service\<resource group> within Server Explorer. I can't see the individual slots, though I don't know or remember if that was possible previously...
I'm having a similar issue. Mine is a bit more complicated in that I have multiple subscriptions and the App Service node under Azure is only displaying the app service (web site) for my MSDN subscription but nothing from my corporate subscriptions. Yet all the other nodes like SQL Databases does show the complete list across all subscriptions.
Fixed! I updated the Azure tools to version 2.6 (I had 2.5). I then right-clicked on the Azure node and selected "Manage and Filter Azure Subscriptions". I made sure that all my subscriptions were selected and then clicked the tab "Regions" and made sure all the regions were also selected. I previously had filtered the regions to only North America as I have no intentions of creating a website in Asia...;)
After I saved the changes the Azure node refreshed and all the sites appeared as expected. I think the core issue was the filtering of the regions. Even though all my sites are located in Central-US and that check box was clicked, it wasn't until I removed all filtering for Regions that my sites finally appeared.
I created a website in the Azure portal, but now I can't find out how to import this into a TFS project. I have visual studio 2013. They seem completely disconnected in terms of importing a project from what the Azure portal creates. Thanks!
Jerelo - the way you solve your issue depends what type of website you deployed and how it was deployed originally. Many of the pre-baked Website images for items like Drupal or Wordpess are not designed to be imported into TFS and auto-deployed.
You would need to download your files via FTP (http://blogs.msdn.com/b/kaushal/archive/2014/08/02/microsoft-azure-web-site-connect-to-your-site-via-ftp-and-upload-download-files.aspx) and then setup source-control deployments by selecting the "Set up deployment from source control" option in the Portal.
Visual Studio Online is the only TFS source you'll be able to use right now, otherwise you have Dropbox, Git or Mercurial deployments Detailed options are listed here: https://github.com/Azure/azure-content/blob/master/articles/web-sites-deploy.md
I enabled the Web Deploy feature for my Web Role and deployed it.
But how can I get hold of the .publishsettings file so I can create a Publishing Profile for it?
This 2 year old article states that it should have been created automatically, but I haven't got that in my profile manager.
Any ideas?
If you are using Visual Studio 2012 or greater, the server explorer to the left will have several Azure items.
Specifically the Windows Azure Compute is what we are looking for, right click on that and say 'add deployment environment'. You will then be prompted with a dialog that allows you to sign in and download publish settings file:
You can get publishsettings file from the following link: https://windows.azure.com/download/publishprofile.aspx
Well, the problem was really behind the keyboard.
So the publishing profile is actually provisioned correctly and automatically to the Web project as the documentation states.
The problem and confusion was that I have a secondary web application in my Solution that I also publish to the same Web Role (referenced as an additional Site in the ServiceDefinition.csdef file).
That Web Project does not get the Publishing Profile, and when I try to create a profile manually, it doesn't work since that (secondary) IIs instance is not configured for Web Deployment.
Oh well, back to the tedious Cloud Service deployment it is...
I am looking at migrating a dotnetnuke website to Azure. I need both staging and production versions of the site to be running.
I have looked at using Azure Websites, but at the moment there is no support for SSL on custom domains so this can't be used for the production website. I have migrated the staging site to an Azure Website and now have numerous options for publishing updates (ftp, git, using web matrix).
Due to the constraints of Azure Websites, I used the DNN Accelerator to create a cloud service for the production environment. This set up will allow me to have control over IIS and therefore manage SSL certificates (I think).
The problem I have with this is there does not seem to be any publishing options. The only way I can publish is by connecting to the Azure instance via RDP and then copying the website files onto the files system.
Are there any other ways of publishing? I have looked at converting the website to a WAP, but I believe this has implications when it comes to updating to new DNN versions.
You should never publish your application through RDP since these changes are non-persistent (meaning what you published might disappear after a hardware failure / ...). Adding new instances would also mean that these instances don't have the files you published before.
I suggest you start by looking at the DotNetNuke Azure Accelerator first. If this doesn't fit your needs you might always try to build something yourself, but if you want to say with a regular website and not a web application I wouldn't count on Visual Studio support. In that case you might want to look at creating a package from the command line and using startup scripts to add your website in IIS.
Sounds like you need to use a Start-up task to install the files in the correct place for a Web Role (Cloud Service) Smarx has a nice overview here, MSDN has a wealth of info too http://blog.smarx.com/posts/introduction-to-windows-azure-startup-tasks
Another option is IAAS for Azure with a persisted VM, more work mind you, Cloud Service would be the most efficient and correct solution...