Why is there a specific version of MongoDb for windows azure? The normal windows version seems to work just fine? What's the difference between those two?
This seems to be the case for a lot of applications, including memcached which someone have made a windows azure port of.
Why would I use a windows azure version of any application? What do I gain?
Why is there a specific version of MongoDb for windows azure? The normal windows version seems to work just fine? What's the difference between those two?
The normal MongoDB install requires an existing Windows environment.
The MongoDB Installer for Windows on Azure includes the provisioning of Azure VMs as well as installation of MongoDB. Provisioning options can also include selecting an Azure data centre location and creating multiple VMs for a replica set.
There is also a package to deploy MongoDB Worker Roles using Azure's Platform-as-a-Service instances.
Why would I use a windows azure version of any application? What do I gain?
If you use the normal Windows installer, you have to create the Azure instances yourself and then download & install MongoDB. If you are creating a replica set you will have to repeat this for each node and add the configuration manually.
The Azure installer simplifies the number of manual steps needed to get your deployment up and running.
Related
We are busy migrating our application from a classic Cloud Service to a new App Service model.
We've done this before, but are now stumbling to something strange and I'm suspecting it might have something to do with the underlying operating system.
The Cloud Service is running on a VM with the Windows Server 2016 family installed (OS Version: 10.0.14393 according to this link: https://www.gaijin.at/en/lstwinver.php)
From what I can tell, the App Service Plan has a much older operating system installed, because Kudu is giving me the following OS information
OS version: Microsoft Windows NT 6.2.9200.0
Which apparently is Windows Server 2012.
In order to test my hypothesis I want to upgrade the OS version of the App Service Plan, but I can't figure out how to do this or even if this is possible.
Yes, currently, web app is hosted on Windows Server 2012.
In order to test my hypothesis I want to upgrade the OS version of the
App Service Plan, but I can't figure out how to do this or even if
this is possible.
Currently, it is not possible. Now Azure Web app is not supported on Windows Server 2016. Based on my experience, it will supported in the future.
Hi I have a console app which I need to start up when Windows Server 2012 starts and without needing to login. I've done a bit of research and people advise a windows service is the correct approach, however the links are quite old and I wanted to confirm this is still the case, or indeed correct at all. Cheers.
Yes, Windows Service is still the most popular way to write and run servers and or a 'daemon' in Windows OS.
Depending on what your application is doing, you might have other options though, e.g. hosting an application in IIS (Microsoft's Web server application in Windows Server).
More recently, Microsoft has been working with Docker to also allow the use of containerized application deployments, which is available in new versions of Windows Server (Windows Server 2016).
Here are a few resources for more reading:
For .NET developers: Walkthrough: Creating a Windows Service Application in the Component Designer
Not just for .NET developers: Quick Start: Windows Containers on Windows Server
I'm a very beginner in Windows Apps. I created a Windows Service app to send mail automatically at a specific time daily. Its taking some configuration values from app.config file. Also there is a web reference too in the service application. Then I installed the app using
InstallUtil /i %myapppath%\windowsservicevb.exe
It worked fine. But with less knowledge in this Windows service application I've no idea how to install that in Azure. Do I just need the exe file or I need to copy the app.config file also into the same directory in Azure?
You need to migrate your windows service on to a worker role in azure if you are going for azure PaaS. example here - http://blogs.msdn.com/b/mwasham/archive/2011/03/30/migrating-a-windows-service-to-windows-azure.aspx
Although if you are on an azure - IaaS VM then it is going to be the same as in the case of a windows machine locally.
Is it possible to automatically deploy to a Windows Azure VM after a successful build from Visual Studio/TFS?
You question is not totally clear if you are looking for a solution for Windows Azure Virtual Machines or Windows Azure Cloud Services.
Windows Azure Virtual Machines:
With Windows Azure Virtual Machine, you own your Virtual Machine and thats why you would need to configure any deployment mechanism you decide. The OS VHD deployed for Windows Azure could be the one you upload or the one you got for gallery, so there are no basic deployment services running unless someone configure them first. For example if you will choose Windows Server based Windows Azure Virtual Machines, then you can install Web Deployment Services in Azure VM, and then configure your VS/TFS to continious deploy it or you can setup FTP based services to deploy your app. This SO discussion talks more on this regard.
Windows Azure Cloud Service:
If you are looking a solution directly from VS then you can add post build scripts using Poweshell commands. This solution will not depend on TFS at all. There are a few solutions also described which are non powershell dependent as well.
Using Visual Studio and Team foundation server components you have ability to configure the combination of MsBuild and PowerShell scripts as described here and here (same as Herve).
If you are looking for a solution directly from Windows Azure TFS (Cloud Based), this article includes everything needed.
You can find some information about automatic deployment here: http://www.windowsazure.com/en-us/develop/net/common-tasks/continuous-delivery/
I am using Amazon EC2 for the first time, and need to create an instance that runs Windows, MSSQL Server 2008, .Net Framework 3.5 SP1 and IIS Server 6.0. I am unable to decide what AMI (out of the huge list of community AMIs) should I choose to meet my requirements. Is there a way I can make this decision without doing trial and error.
You can take a look through the list of available Windows AMIs on the AWS web site; if you sort by title you should be able to spot suitable candidates fairly quickly.
You may be out of luck with the particular combination of versions you're looking for, since most installations of MSSQL Server 2008 are likely to be on Windows Server 2008, which usually has IIS 7.0 installed rather than 6.0.