How to find Windows Server and Visual Studio version used in agent pool that are configured in azure devops .
You can find all OS and Visual Studio versions here: https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops#use-a-microsoft-hosted-agent
The development machine does not have enough capacity to host and run the Service Fabric cluster on the same machine where VS 2019 installed. So, a possible workaround would be having the cluster created on the local network (not Azure) and debug it remotely. Is it a feasible scenario, and if so how we can configure VS 2019 to remotely debug the application?
We have a doc for remote debugging a SF application using VS
https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-debugging-your-application#debug-a-remote-service-fabric-application
It doesn't appear it has been updated for VS 2019 though so some steps might be a bit different. But it is possible and should give you a place to start.
Is it possible to debug a .NET Core application running in a Linux Docker container from another (remote) Linux/Mac/Windows developer machine running Visual Studio Code?
The goal
I would like to use a Windows Server 2016 (x64) for remote debugging of UWP applications. The reason? My working PC still runs a Windows 7 instance and it is not possible to deploy an UWP app on a Windows 7 machine.
The problem
I have already installed the Remote Tools For Visual Studio 2015 on the Windows Server 2016 machine and started it on port 4020. Authentication mode was set to "None". I have enabled Developer mode on the server as well. Also I have set up my project in Visual Studio to use the remote machine for debugging.
The problem is, whenever I try to deploy (just deploy, not even debug) my solution to the server, the following happens:
Visual Studio shows the following output:
Deploy started: Project: MyProject.UI.Uwp, Configuration: Debug x86
Starting remote deployment...
Reading package recipe file "C:\SourceCode\MyProject\MyProject.UI.Uwp\bin\x86\Debug\MyProject.UI.Uwp.build.appxrecipe"...
and then hangs forever.
In the meantime, remote tools on the server show the following output:
UserAbc connected.
This indicates there must be at least some communication between my Windows 7 PC and the target Windows Server 2016 machine.
No error message is displayed whatsoever (neither in Visual Studio, nor in the Remote Debugger).
The question
Any idea why the deployment hangs forever without an error message? Or am I trying to achieve an impossible task? Is the Windows Server 2016 capable of running UWP apps at all?
Update
I installed VS 2015 Update 3 directly on the Windows Server 2016. I was able to create and debug a simple UWP app directly on the server so the server is clearly able to run an UWP app. However I am still unable to make the remote debugging working. Maybe the problem is completely on my local Windows 7 PC and has nothing to do with the Windows Server. It is strange that the process hangs while "Reading package recipe file". Could it be that an antivirus is intercepting?
Thanks for your feedback. There is a similar issue when I try to deploy the UWP project to a remote machine on Windows 7. We have communicated about this using our internal channel. Unfortunately, Visual Studio 2015 or Visual Studio 2017 doing UWP development on Windows 7 is not a recommend scenario.
For Visual Studio 2017, using Tools for UWP App Development is not applicable on Windows 7. See Visual Studio 2017 Support for Windows Development.
For Visual Studio 2015, the official support for Windows Universal is "Build only". We can use Visual Studio 2015 to build UWP apps on Windows 7, but some other Visual Studio features for Windows Universal development may be degraded. See Visual Studio 2015 Support for Windows Universal, Windows Store, and Windows Phone App Development.
To develop Windows Universal Apps, Windows 10 is strongly recommended. With Windows 10, you can get the best experience of UWP development.
We have a two servers on farm. We issue using Visual Studio's "deploy" action where it can't install the feature because it couldn't be found :
Error 1 Error occurred in deployment step 'Activate Features':
Feature with Id 'XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX' is not installed in this farm, and cannot be added to this scope.
It seems like Visual Studio will only deploy to one server, and we've evidenced that with a project that just had a package and the package only deployed files to the server with the URL. But it doen's worked for us, too.
Does anyone have any idea on what we can do to get the VS 2012 deploying to work when you have two servers for SharePoint 2013?