azure-web-sites

I've got to a website and a webjob project in the same sln: Sritt (The website) Sritt.Webjob In properties of Sritt theres a webjobs-list.json with the following setting: "WebJobs": [ { "filePath": "../Sritt.WebJob/Sritt.WebJob.csproj" } I've configured the by VSTS build like this (with the new buildsystem): Solution: **\*.sln MSBuild Args: /p:DeployOnBuild=true /p:WebPublishMethod=Package /p:PackageAsSingleFile=true /p:SkipInvalidConfigurations=true /p:PackageLocation="$(build.stagingDirectory)" Building in VSTS gives me the following warning: C:\a\1\s\packages\Microsoft.Web.WebJobs.Publish.1

I was wondering if there is an easy way to completely copy all the key values from one web app's application settings to another, as seen in the below picture I have a lot of these key values and having to do this manually every time is very cumbersome. You can use Azure PowerShell. Here is a PowerShell Script for you. try{ $acct = Get-AzureRmSubscription } catch{ Login-AzureRmAccount } $myResourceGroup = '<your resource group>' $mySite = '<your web app>' $myResourceGroup2 = '<another resource group>' $mySite2 = '<another web app>' $props = (Invoke-AzureRmResourceAction -ResourceGroupName

We have deployed our Sitecore CMS on to Azure Web Apps and having some indexing issues or similar. i.e. the updated changes is reflected for some users and not for all. We have a scale turned on to 2. I would like to troubleshoot by accessing the instance 1 and 2 directly via URL to make sure both instances have index built 100%. How do I access each Azure Web Role instances directly via URL? Thanks. The first step is to get the list of instance names. There is an Azure API for it, which you can easily invoke using Resource Explorer ( https://resources.azure.com/ ). Use these steps: In

Out of the blue our Azure web app is spewing out errors regarding a Culture that is not supported. We load up a list of countries to show on the front page but this is suddenly giving errors. The same code is used on other various web apps as well and they aren't having the problem. The following code gives a problem. private List<SelectListItem> Countries() { RegionInfo country = new RegionInfo(new CultureInfo("nl-BE", false).LCID); List<SelectListItem> countryNames = new List<SelectListItem>(); foreach (CultureInfo cul in CultureInfo.GetCultures(CultureTypes.SpecificCultures)) { country =

I have an app on ASP.NET 5 (CoreCLR) and I try to publish it to the Microsoft Azure. I using free Web App (not VDS) I am publishing app using Visual Studio 2015 Publish->Microsoft Azure and following this instructions . But when I publish it and try to open, I see just non-stop loading of empty page. I enabling logging and view the log (stdout.log) from Azure and there was only: '"dnx.exe"' is not recognized as an internal or external command, operable program or batch file. Also I tried to do Continiusly publishing with git. During push, It started restoring packages and failed with error no

I have a project and I'm planning to start the web app as an Azure Web Site and then migrate it to an Azure Cloud Service (also called Hosted Service) if it is needed as a scale strategy. The decision is because I read that Azure Web Sites are more simple and fast to develop with almost no Azure-specific configurations or code. So starting fast and simple is a good starting point for the project. But, is that a good starting point for you? Is migrating an Azure Web Site to an Azure Cloud Service the same as you were migrating a normal ASP.NET Website to an Azure Cloud Service? Would you start

I am using the "Azure Web App Deployment" build step in VSTS to publish an ASP.NET Core API to an Azure Web App: Occasionally, this step breaks with the following error: [error]Microsoft.Web.Deployment.DeploymentDetailedClientServerException: Web Deploy cannot modify the file 'MyProject.Api.exe' on the destination because it is locked by an external process. In order to allow the publish operation to succeed, you may need to either restart your application to release the lock, or use the AppOffline rule handler for .Net applications on your next publish attempt. Learn more at: http://go

I've been investigating a slow warmup time for my production app and I got some unexpected results. Testing on various Azure VMs showed the warmup time to be well-related to the application server performance (so it's not external request, including sql), but what's really interesting is the comparison to Azure Web Apps and my own local machine (all times are averages from at about 3 runs): VM A0: >1m VM A2: 13s VM D2V2: 6.8s VM D5V2: 7.8s Wep App P2: 25s Web App S2: 26.5s My local machine: 6.6s My local machine is an i5 with 3.3GHz. The local machine is fastest even though it connects to the