Whenever I try to attach a debugger to my Azure server, I get this error:
I already installed Azure SDK for Visual Studio 2015. Any idea why this happens?
Related
I have deployed the following API as is to an Azure App Service from Visual Studio.
I have made sure that I have Remote Debugging and Visual Studio version 2022 selected in General settings in the App Service Configuration.
When I try and attach process from Visual Studio to my App Service I get thefollowing error:
In VS 2022, We have an easy and direct way to attach debugger.
After publishing your WebApp, In Hosting settings we will find an option to Attach Debugger.
Once debugger is attached, Remote debugging is enabled in Portal => Configuration Settings automatically.
Place a break point in any of the form which you want to debug.
Visual Studio finds the process, all the symbols will be loaded, and debugger is attached.
I have an Azure Cloud Service solution in Visual Studio 2017 which I debug with Emulator Express.
I'd like "migrate" from Visual Studio to Visual Studio Code. I mean that I'd like to be able to run/debug my cloud service(web role project) in VSCode without the use of Visual Studio at all.
My solution has two project:
Service project - contains .csdef, .ccproj and multiple .cscfg.
Role project - contains the .csproj file and the rest of the sample web role project.
I've tried:
I'm building both of the projects with msbuild, the same way it's been built in visual studio. The problem is running the site locally.
Run a local site with IIS Express VSCode extension and configure the web role project root as site root. It didn't work, I tried to browse the site but I got a notification that the folder of the site can't be viewed as a directory. When I think of it this option is missing all the configuration that is defined in the Service project so how is it suppose to work? Does IIS Express can run an Azure cloud service app locally? Maybe I configure a wrong path?
I've tried running csrun.exe command multiple times with different arguments. Something like this:
"C:\Program Files\Microsoft SDKs\Azure\Emulator\csrun.exe"
/run:./csx/Debug/roles/WebRoleProject/approot;./ServiceConfiguration.myconfig.cscfg /launchBrowser
/launchDebugger:%systemroot%/System32/vsjitdebugger.exe
It gave me the following error:
The compute emulator had a error: Can't locate service descriptions..
I also saw here that compute emulator(csrun.exe) needs visual studio opened as administrator, so maybe it's not possible to run it without it..
I’ve verified this question with the Azure Cloud Compute team and this is not supported in VSCode, they only built an extension for Visual Studio.
I am trying out CosmosDB and Visual Studio Mac for the first time and I'm getting errors such as
The base class associated with this Xaml file could not be found
/Users/Downloads/DocumentDB-Quickstart-Xamarin/packages/Xamarin.Forms.2.3.3.180/build/portable-win+net45+wp80+win81+wpa81+MonoAndroid10+Xamarin.iOS10+xamarinmac20/Xamarin.Forms.targets(3,3): Error MSB4018: The "XamlCTask" task failed unexpectedly.
System.IO.FileNotFoundException: Could not find file "/Users/Downloads/DocumentDB-Quickstart-Xamarin/iOS/obj/iPhoneSimulator/Debug/DocumentDBTodo.iOS.exe.mdb".
File name: '/Users/Downloads/DocumentDB-Quickstart-Xamarin/iOS/obj/iPhoneSimulator/Debug/DocumentDBTodo.iOS.exe.mdb'
All I did was
Create a cosmos db using the SQL/DocumentDB access
Click on quickstart and download the Xamarin cosmos db quickstart
Build and Run
Was there something in my setup that I'm missing?
The template has not been updated with the latest Xamarin.Forms and VS is not being able to compile the code.
Update the Xamarin.Forms package manually by right-click (over the package) -> Update. Once updated clean and rebuild your project and you will be good to go.
Hope this helps.-
I have just upgraded to VS2015 and when I try to connect the Remote Debugger to an Azure web app, I get this error:
The following error occurred while launching remote debugging: Unable
to connect to the Microsoft Visual Studio Remote Debugger named
'xxxxxxx.azurewebsites.net'. The remote debugger is older than this
version of Visual Studio 2015, and Visual Studio is no longer
compatible with it. Please upgrade your remote debugger to match
Visual Studio.
I have checked the Azure Web App settings and Remote Debugging is on, and VS2015 is selected as the remote debugger.
The Azure App Service Support - Event Viewer is reporting this warning
Msvsmon was unable to start a server named '127.0.0.1:50245'. The
following error occurred: An instance of the remote debugger is
already running on this computer, or another process is already bound
to the specified TCP/IP port. View Msvsmon's help for more
information. 08005E80
I guess this is problem but how do I resolve it?
Make sure you deploy a 'DEBUG' build of your application to Azure App Service from Visual Studio 2015. If the debugger still won't connect, you could try making sure to have the latest updates installed to your local Visual Studio 2015, then try it again.
I'm having trouble starting Azure Emulator on my Windows 8.1 laptop. I use Visual Studio 2013. The error I'm getting is:
Windows Azure Tools: Failed to initialize Windows Azure storage emulator. Operation is not supported on this platform.
The project I'm trying to build was developed first in VS 2012 so VS 2013 changed some files for me for compatibility reasons.
I tried searching for this issue, but I haven't found any page regarding this error.
Anyone have any other ideas?
It looks like a problem of Azure storage. You may want to check what version of Sql is installed on your laptop. Find this post can be helpful http://social.msdn.microsoft.com/Forums/windowsazure/en-US/6fafe385-8f1a-4add-b782-3c0761505695/failed-to-initialize-windows-azure-storage-emulator?forum=windowsazuredevelopment