Can Web application hosted on IIS still use Azure App Fabric - azure

I hosted web app into IIS? Can I still use Azure App Fabric caching services for session? All the samples that I see says first I have to create a web role and then configure app fabric caching service for session mgmt. Is there a way I can configure app fabric caching service for regular web applications?
Thanks

Yes, you can use app fabric to monitor wcf and wf workflows and for caching:
here's some useful links:
http://social.msdn.microsoft.com/Forums/en/velocity/threads
http://www.hanselman.com/blog/InstallingConfiguringAndUsingWindowsServerAppFabricAndTheVelocityMemoryCacheIn10Minutes.aspx
http://msdn.microsoft.com/en-us/library/ff383731(v=azure.10).aspx

Related

Migrating Web service to Azure

I think, previously cloud services (classic) used for any web service deployment.
What Azure service to choose for migrating Web service or Web API or WCF service ? What needs to be considered before and after migration. Is there any guide available?
Thanks.

Why should I prefer Azure App Service over .NET REST Web API?

Why should I use Azure App Service and not just implement a common .NET RESTful Web API backend?
What's the explicit benefit of this service compared to a common .NET RESTful Web API backend hosted on Azure?
An Azure App Service is a place to host your web application or API. Normally when you have a .NET web API you host it behind IIS or something on a virtual machine.
Azure helps you with these common scenarios wit Platform as a Service (PaaS). An App Service completely abstracts the operating system and the way you host your web application.
App Service can host web apps both on Windows and Linux. You can use all kinds of frameworks such as PHP, .NET or Java. You can even host containers without worrying about the host.
A good sample to start with hosting your .NET Web App on Azure App Services can be found here: Quickstart: Create an ASP.NET Core web app in Azure
Yes, there is a huge difference between Azure App Service and .Net REST WebAPI backend on Azure.
Hosting on Azure can be done using two ways
Create your own VM, then install IIS and do all the required stuff
Use AppService Plan
AppService Plan allows you to leverage the powerful functionality of Azure. Here a separate VM is not assigned to you. Azure App service can scale automatically depending upon the Scaling rule which is not present in restful API hosted on Azure VM.
My question blatantly was a stupid Newbie question, and as such, I'm afraid it is non-sense, which I now know by the answers you've given.
I'm currently reading the book "Azure and Xamarin Forms" to learn Xamarin and Azure. Apparently it's outdated. It suggests to "create a Mobile App on Azure". From the book that Mobile App is just a plain App Service running a RESTful Web API with EF, but utilizing completely different namespaces to do so.
My question targeted towards these other namespaces. I didn't see a reason for them.
Apparently, Microsoft noticed the same. There is no "Mobile App" available in the Azure Marketplace anymore.
Azure App Service is a PaaS solution from Microsoft hosted on Azure. You can think of Azure App Service as some sort of "Micrsoft Heroku", because they work on a similar fashion. For many REST Projects, it can save you hours, if not DAYS of development. It has automatic TLS like heroku, but it is hosted on Azure instead of AWS and it can integrate very well with your existing Azure resources. One common pattern is to host the REST API on App Service and use a database service from Azure such as Azure SQL or Cosmos DB (which is a NoSQL service that, from the point of view of your app, it operates as MongoDB, but can be configured to behave as other DBMS).

Is it possible to use MQ Client with a web app installed in an Azure App Service?

We have a web app running on Windows Server but we need to migrate it to an Azure App Service.
Our web app uses MQ Client service to connect with certain transaction services, but it is not possible to install other services on the Azure App Service except for the web app.
Is there a way to use MQ Client in Azure?
Thank you very much for your time!
Is there a way to use MQ Client in Azure?
As Azure WebApp is a sandbox. Install MQ client is not supported on the Azure WebApp service.
If Azure VM is acceptable, I recommand that you could use Azure VM to instead of Azure WebApp service in your case.

microsoft azure hosted database and firewalls

I am doing mobile development on Xcode and using hosted database from Microsoft Azure.
I noticed there is firewall settings on Microsoft Azure in order to add clients.
How will this work when the mobile app is deployed? Should all ports be opened on the database? Or do I need to use Web Services?
How will this work when the mobile app is deployed? Should all ports
be opened on the database? Or do I need to use Web Services?
You should definitely NOT open all ports and direct connectivity to the database from mobile apps is strongly discouraged.
Recommended way would be to use some kind of service layer sitting between your mobile app and the database. All the requests from the app should go to this service layer which will perform database operations. This service layer could be deployed as Azure Mobile App Service, Azure API App Service or a Web API hosted in Azure Web Apps Service.

Is it possible to configure a virtual application to use a separate app pool in azure web apps?

We've recently migrated our site from Azure Cloud Services to use Web Apps.
Previously we had one main website application, which has a virtual application at /forums - in cloud services we configured this to use a separate app pool to the main website.
Whilst we've had no issues adding a virtual directory and deploying to it, we seem to be unable to configure a separate app pool, is there anyway to achieve this?
Here is a description on the Azure site, Migrate an enterprise web app to Azure App Service
Application Pools – In Web Apps, each site and its child applications run in the same application pool. If your site has multiple child applications utilizing multiple application pools, consolidate them to a single application pool with common settings or migrate each application to a separate web app.
So it seems that currently, we cannot achieve this.

Resources