How to prevent an Azure website from going to sleep?
I deployed an ASP.NET 5, MVC 6 web application to Azure. It seems that if I don’t hit the site for 10-15 minutes, it goes to sleep and it takes a good 10-15 seconds for it to wake up.
I deployed an ASP.NET 5, MVC 6 web application to Azure. It seems that if I don’t hit the site for 10-15 minutes, it goes to sleep and it takes a good 10-15 seconds for it to wake up.
Azure websites have a default “site URL” provided by Azure, something like mysite.azurewebsites.net. Is it possible to get this URL from inside the website itself (i.e. from the ASP.NET application)?
I have an ASP.NET MVC 5 app where I need to invoke wkhtml2pdf.exe in my Azure website using Process.Start. Locally everthing works fine. But it seems my app stuck at Process.Start line. Is starting a process is supported on Azure?
I have web application for running unit tests for our data and I want to deploy it as Azure Web Site.
The problem is in this app I’m downloading quite large zip files, extracting them (~50MB, 500 files inside) and doing some tests over these files.
Where should I save these large files on Azure Web Sites and where hould I extract them? On localhost I’ve been using “Path.GetTempPath()”, but Azure Web Site is reporting that there is no space in this folder, even though my Azure Site has 1000MB total and about 990MB free.
Is there any way how to use these 1000MB for my file operations?
In case this is not possible, should I use the Azure Blob Storage for the extracted files?
We have an Active Directory domain sitting on a networked Azure VM and have a separate Azure WebApp/Website that is running Orchard CMS on the same virtual network.
We have an ASP .NET (MVC) app and are using Entity Framework 6 to connect to our databases. The DbContext is constructed in a standard way and it loads the connection string on our behalf. The generated code looks like this:
I am trying to understand the impact of setting ThreadPool.SetMinthreads. I have multiple virtual applications running in one Azure App Service. My understanding is that all these virtual applications will share the App Pool, and will have only one worker process (Assuming the App Pool’s max worker process will be 1).
Something that seems to be absent from the otherwise great new features for Windows Azure (announced on June 7th), is the ability to define distributed caches for the reserved instances of a Website Cluster in Reserved Instance Mode.
I’m trying to deploy my web app to Microsoft Azure and everything goes fine in visual studio. But when it launches it shows: