azure-emulator

azure emulator not starting for web role if node_modules directory exists

由 空扰寡人 提交于 2020-01-13 16:18:42
问题 I think I just stumbled on a really weird problem. I have a pretty big solution including one azure project with 3 roles, two worker and one web role. The web role is based on asp.net mvc and web api. After experimenting with gulp yesterday (for compiling and bundling less files), I noticed just now that the azure emulator won't start this role anymore. The emulator start dialog just stops at ~ 80% and stays there forever, without any error messages. After I removed the node_modules directory

Bind the Azure Emulator to all addresses of its host?

由 折月煮酒 提交于 2020-01-06 02:36:29
问题 Is it possible to bind the Azure Emulator to all of the addresses on the host? The default configuration binds the emulator to a single address, the loopback address - 127.0.0.1. I can successfully change the single address that it binds to in its config file: %Program Files%\Microsoft SDKs\Windows Azure\Emulator\devfabric\DevFC.exe.config By changing VipPoolStartIPAddress and VipPoolEndIPAddress : <add key="VipPoolStartIPAddress" value="192.168.1.130" /> <add key="VipPoolEndIPAddress" value=

Azure Emulator stuck

由 元气小坏坏 提交于 2020-01-04 13:38:29
问题 I'm working on azure WorkerRole project in VS2015 , SDK 2.9 . The role works good in cloud, but when i'm trying to run it locally with FullEmulator, role can't be started: [fabric] Role Instance: deployment29(116).MyComp.Engine.Deploy.MyProject.Engine.Azure.0 [fabric] Role state Unknown [fabric] Role state Busy [fabric] Role state Unknown [fabric] Role state Busy [fabric] Role state Unknown [fabric] Role state Busy [fabric] Role state Destroyed [fabric] Role state Busy looks like role is

Role in Azure Compute Emulator stuck cycling between Unknown and Destroyed states

由 ＊爱你＆永不变心＊ 提交于 2019-12-17 17:16:43
问题 My Azure Cloud Service's Web Role works fine when deployed to Azure but can't get it running with the Emulator. When starting the role from within Visual Studio (2015) the window just displays "Starting the roles for the application in the Microsoft Azure compute emulator...". When starting with the debugger OnStart() doesn't seem to be hit at all, so something before that gets stuck. The role doesn't seem to be started because the app's custom logs are not created either. Looking at the

Azure Emulator appears to hang on Web Role startup

由 孤街浪徒 提交于 2019-12-13 02:06:27
问题 I am trying to use the Azure emulator to debug a .net solution for VS2013, I am using IIS Express and Emulator Express. The project contains several worker roles, which start just fine, and one web roles that seems to hang intermittently. The weird thing is that if I reboot the computer and restart the debugger, it seems to work. I see the following lines if I click on the "Show Compute Emulator UI" option, Web Role: [fabric] Role Instance: deployment28(2907).MyApp.Cloud.MyApp.Web.0 [fabric]

azure emulator not starting for web role if node_modules directory exists

由 我的梦境 提交于 2019-12-05 20:16:43
I think I just stumbled on a really weird problem. I have a pretty big solution including one azure project with 3 roles, two worker and one web role. The web role is based on asp.net mvc and web api. After experimenting with gulp yesterday (for compiling and bundling less files), I noticed just now that the azure emulator won't start this role anymore. The emulator start dialog just stops at ~ 80% and stays there forever, without any error messages. After I removed the node_modules directory, everything worked fine again. The web role itself doesn't use anything nodejs related, but gulp seems

Role in Azure Compute Emulator stuck cycling between Unknown and Destroyed states

由 让人想犯罪 __ 提交于 2019-11-28 02:26:00
My Azure Cloud Service's Web Role works fine when deployed to Azure but can't get it running with the Emulator. When starting the role from within Visual Studio (2015) the window just displays "Starting the roles for the application in the Microsoft Azure compute emulator...". When starting with the debugger OnStart() doesn't seem to be hit at all, so something before that gets stuck. The role doesn't seem to be started because the app's custom logs are not created either. Looking at the Compute Emulator's UI reveals that the role is continuously (and very slowly) cycling between Unknown and
订阅 azure-emulator