I migrating project to Azure sdk 2.2 and new Visual studio
In full emulator webrole starts long time. At first I thought that it didn't start. But happened to notice that after 15 minutes it starts and works fine.
In emulator of VS 2012 it works fine.
In deploy it works fine.
In express emulator of VS 2013 it works fine too.
Someone has Any ideas, how I can find a solution for startup time in emulator from VS 2013?
Update: I found a problem. In VS2013 discontinued Visual Studio Development Server and I need to configure Full IIS
Related
I recently installed Visual Studio 2017 and my problems began with remote debugging.
So, this is the message error.
And on Azure, they are lagging behind the official release of VS Remote Debugging for this VS version.
Any idea on how to make this work?
If you use Cloud Explorer within Visual Studio 2017 to initiate the Remote Debugging it'll set the VS Version on the Web App correctly. Currently, the portal doesn't include UI to allow you to set 2017 as the version, but using the Cloud Explorer to initiate remote debugging will do it behind the scenes. We just need to wait for the Azure Portal to be updated and get caught up with VS.
Visual Studio 2017 is now listed as a Remote Debugging Version in Azure.
There has however been some change on what is possible on Cloud Explorer. To access the 'Attach Debugger' option, you need to use the Server Explorer.
I've got problems running the Azure Emulator, the web role gets Unhealthy status.
The problems started today after a Windows Update installed several new updates. Yesterday all worked fine.
I've tried to create a new empty Cloud Service project in Visual Studio 2015 with Azure SDK 2.7. The emulator startup dialog loads to 3/4 of the progress bar and when I look into the Compute Emulator the Web role is stated as Unhealthy.
After a while Visual Studio hangs and I have to kill the process.
I've tried the following
Updating Visual Studio
Reinstalled Azure SDK 2.7
Uninstalled all previous versions of the SDK
Restarted the computer several times
No luck whatsoever. I'm running out of ideas and would appreciate some help.
Solved the problem by repairing the Visual Studio installation. Works fine now.
I used to be able to open an FTP website in Visual Studio 2012 until recently when it stopped working correctly. I can connect to my server using FTP and I get the full folder list of my servers websites, but attempting to open any file in any of the folders (asp.x,aspx.vb etc) Visual Studio just hangs - has anyone else experienced this, and if so how was it resolved?
Thanks.
I had the same problem today. I've installed Visual Studio updates (through visual studio update checker) and everything works fine now
I have had nightly builds set up and working for a few months until now. I installed Visual Studio 2012 SDK on Saturday and now my builds are not deploying via MSDeploy.
My build server has Visual Studio 2012 installed. It also has the admin console for both TFS 2010 and 2012 installed. We aren't using 2012 yet so I have the service turned off.
In my build definition, under Process/Advanced/MSBuild Arguments, I have this:
/p VisualStudioVersion=11.0;DeployOnBuild=true;DeployTarget=DeployToDEV;username=xxx;password=xxx;WebPublishPipelineProjectName=dev
My project has a targets file called dev.wpp.targets. Inside of this file I have a DeployToDEV target. I basically followed the instructions from "Inside the Microsoft Build Engine" so I can deploy to multiple servers at the same time. It worked beautifully until now.
I get no errors and no indication that Web Deploy has been run or not.
I would really appreciate some help.
Thanks.
I am getting an Exception when I am trying debug my application on Emulator (Web Role).
you can see exception by clicking following link
Configuration which I am using Windows 7 pro, VS 2012 Pro, Azure SDK 1.8
Hope it might help others.
I Also had the similar problem and I restarted PC and **Run Visual Studio as Administrator**.
And let Visual Studio start the emulator with same privilege resolved the issue.
I was using Visual 2013 and Web API application under IIS Express.
Do you have IIS added? Most likely it's already installed but you've to enable it via Add Windows Compoenents on Control Panel...
I had this same issue all of a sudden, luckly I remember changing the ServiceDefinition.csdef file. I rolled this back to an earlier version and the debugger ran again correctly. The only thing I changed in the 'broken' version was instance size from small to medium.
Go to visual studio installer(search it from window's start)
and update the visual studio.
After updating, hit modify
button, after that on right side you will find a box named
debug (or something like that), select that box
Then hit install.
Restart your visual studio and debugger will start working.
In my case it worked perfectly.