I created a clean Web API .NET Core project and published it, using the default settings, to an Azure App Service, also created using all the defaults. Then I started up Visual Studio 2017 in Administrator mode and tried to attach the debugger. I got:
Unable to find a process called dotnet with arguments
.\MyCompany.WebApi.dll. The process may still be
starting, please try again.
What is wrong? Has anyone successfully debugged a App Service with .Net Core remotely. Seems like kind of a limitation of the environment if not.
EDIT: I upgraded to Visual Studio 2019 and was able to remotely debug processes running in Azure. There seems to be a critical failure with 2017 and Microsoft can't support it.
Related
I have been able to run Azure cloud services locally before, but Emulator Express is not available anymore.
The same problem appears on two Windows computers.
How to reproduce:
Download https://code.msdn.microsoft.com/Simple-Azure-Cloud-Service-e01df2e4 and unzip it.
Open the project in Visual Studio 2017 v15.9.6
Follow https://learn.microsoft.com/en-us/visualstudio/azure/vs-azure-tools-emulator-express-debug-run?view=vs-2017 to verify that IIS Express and Emulator Express are selected
Try to run the Azure Could Service in Emulator Express.
In step 4, I only have this option in the toolbar:
If I use that, my Frontend role starts, but the Worker Role does not start.
The same problem exists for one of my own Cloud Service projects.
Installed products in Visual Studio: https://gist.github.com/mfalkvidd/78114c37e16d793c26a44431dad2795d
VS2017 publish causes error on startup "cannot load file or assembly ..." Running directly from the build works but not from the deployment in app.publish folder. The error shows even on my development computer. However, opening the same solution in VS2010 and publishing from there, all works as expected. I cannot find this same issue on the web.
After searching for all things Click Once, I came across an answer for a different issue and tried it. I upgraded the target framework to .NET Framework 4.6.1 and updated the NuGet Packages. Afterward, I was able to publish and run the Click Once Application with no errors.
I am using wso2 developer studio - Luna version in Windows 10. I added a carbon server instance using developer studio and it got added successfully. It is not getting started and stays at 'Preparing launch delegate' as shown in the image.
This link didn't help me: wso2 eclipse server in status [starting] forever
I have set up a CI server for our .NET projects. To build those projects I want to use the Visual Studio executable devenv.exe.
This worked out perfectly during the "evaluation period". Now these 30 days are over, to keep using Visual Studio on my Desktop computer, I just updated my license with one mouseclick. Doing this on the server allows me to build using the GUI, but when running devenv.exe programatically with the required parameters, I am receiving an error that the evaluation license expired, even though I renewed it.
I have already tried a clean reinstall, which did not fix the issue for me. Visual Studio on the server is connected to the same account I am successfully using on my Desktop PC.
Is there a known fix for this issue?
Figured it out. The license is somehow related to the user that launches Visual Studio. So to to automatically build projects with devenv.exe, the building agent has to run under the same user account, that installed an launched Visual Studio.
Did anyone get that to work? I mean, unit testing .Net CF apps on Windows Mobile 6.5.3 in Visual Studio 2008.
It works great for a WM 6 Pro target, but not for a WM 6.5.3 target.
I get this error:
The test adapter ('Microsoft.VisualStudio.TestTools.TestTypes.Unit.UnitTestAdapter,
Microsoft.VisualStudio.QualityTools.Tips.UnitTest.Adapter, Version=9.0.0.0,
Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a') required to execute this
test could not be loaded. Check that the test adapter is installed properly.
Not enough storage is available to process this command.
Yes, I can read the error text, but I don't understand the failed run.
Any clues?
For future reference: The only way I could make this problem go away turned out to be a complete reinstall of the WM 6 SDK and 6.5 DTK. Shortly after that I upgraded to Windows 7 and reinstalled VS 2008 with the 6.5.3 DTK and the shebang, and testing still works as expected.
This error means that CF 3.5 isn't installed on the target device (it's an option, not a requirement for the OEM). You can manually install it, or create a CF 3.5 app (like the app you're testing) and deploy it once to have Studio deploy the CF runtimes.