azure-role-environment

Azure Emulator Won't Accept D-Series Role

由 心不动则不痛 提交于 2020-02-02 10:57:47
问题 If I try to debug an Azure project using the new D-Series sizes, I get an error saying that the Specified argument was out of the range of valid values. I'm using the latest 2.4 tools. Is there a way around this or do I have to wait for 2.5? Another weird issue is that I have to manually edit the csdef and re-open the role properties to even get the choices for the new sizes. I verified that my projects have been upgraded to 2.4 as well. 回答1: This was resolved with SDK v2.5 来源： https:/

Azure Autoscale Restarts Running Instances

由 ╄→尐↘猪︶ㄣ 提交于 2019-12-28 06:44:40
问题 I've been using Autoscale to shift between 2 and 1 instances of a cloud service in a bid to reduce costs. This mostly works except that from time to time (not sure what the pattern seems to be here), the act of scaling up (1->2) causes both instances to recycle, generating a service outage for users. Assuming nothing fancy is going on in RoleEntry in response to topology changes, why would scaling from 1->2 restart the already running instance? Additional notes: It's clear both instances are

Accessing Local Storage in azure

由 岁酱吖の 提交于 2019-12-12 00:28:47
问题 I have a website in azure which I want to create pdfs from templates. I need some where to store the pdf while I'm creating it. After some searching round I thought the best way to handle this would be through Local Storage. I added a Windows azure cloud service project to my web app. I then added local storage to the role for my web app. Locally I can now create pdfs from templates and store them in blob storage. However when I publish the app to azure it no longer works. I thought I might

Azure Autoscale Restarts Running Instances

由 五迷三道 提交于 2019-11-28 00:58:54
I've been using Autoscale to shift between 2 and 1 instances of a cloud service in a bid to reduce costs. This mostly works except that from time to time (not sure what the pattern seems to be here), the act of scaling up (1->2) causes both instances to recycle, generating a service outage for users. Assuming nothing fancy is going on in RoleEntry in response to topology changes, why would scaling from 1->2 restart the already running instance? Additional notes: It's clear both instances are recycling by looking at the Instances tab in Management Portal. Outage can also be confirmed by hitting
订阅 azure-role-environment