How to find Windows Server and Visual Studio version used in agent pool that are configured in azure devops - azure-devops

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

Related

Does Azure DevOps Hosted Pipeline Agent Have Specific Visual Studio Option? (C++/CLI v141 build tools)

I need this option from Visual Studio (2019) installer: C++/CLI support for v141 build tools (14.16):
On this web page, it has links to the software installed on the different host agents, when clicking on Windows 2022 or 2019 it does not show this info:
https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml#software
for example, for windows 2022:
https://github.com/actions/runner-images/blob/main/images/win/Windows2022-Readme.md
How can I find out if this is installed or not?
From the VS2019 doc: https://learn.microsoft.com/en-us/visualstudio/install/workload-component-id-vs-build-tools?view=vs-2019
"C++/CLI support for v141 build tools (14.16)" is categorized under "Microsoft.VisualStudio.Component.VC.v141.CLI.Support" with version 16.3.29207.166
Checking the MS-hosted windows 2019 agent: https://github.com/actions/runner-images/blob/main/images/win/Windows2019-Readme.md
"Microsoft.VisualStudio.Component.VC.CLI.Support" is installed with version: 16.10.31205.252
From the VS2022 doc: https://learn.microsoft.com/en-us/visualstudio/install/workload-component-id-vs-build-tools?view=vs-2022
"C++/CLI support for v141 build tools (14.16)" is categorized under "Microsoft.VisualStudio.Component.VC.v141.CLI.Support" with version 17.4.33006.217
Checking the MS-hosted windows 2022 agent: https://github.com/actions/runner-images/blob/main/images/win/Windows2022-Readme.md
"Microsoft.VisualStudio.Component.VC.CLI.Support" is installed with version: 17.3.32708.82
This build tool is available on both 2019 and 2022 MS-hosted agent, if you want the specific version, another good approach would be using Self-hosted agent: https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/v2-windows?view=azure-devops

Azure devops self-host deploy agent

If I am using a self-hosted deployment agent for my azure devops Ci\CD pipeline , and the pipeline is regarding to deploy Azure databricks notebook and also to build Azure sql database project and deploy dacpac ,
what component is required to be installed in that self-host agent ?
what component is required to be installed in that self-host agent ?
Prerequisites:
• Windows 7, 8.1, or 10 (if using a client OS)
• Windows 2008 R2 SP1 or higher (if using a server OS)
• PowerShell 3.0 or higher
• .NET Framework 4.6.2 or higher
Note - the minimum required .NET version for build agents is 4.6.2 or
higher. If you're building from a Subversion repo, you must install
the Subversion client on the machine.
You should run agent setup manually the first time.
Prepare permissions
Information security for self-hosted agents
Authenticate with a personal access token (PAT)
Confirm the user has permission
Download and configure the agent
Before you install a self-hosted agent you might want to see if a
Microsoft-hosted agent pool will work for you. In many cases this is
the simplest way to get going.
For more information refer - https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=azure-devops&tabs=browser#install

How to get VS build agent capabilities without installing the full Visual Studio application?

I've installed the latest VS Build Tools (2022), but my on-prem build agent isn't picking up the VisualStudio-related capabilities. I've been under the impression that we no longer need to install the full application in order to get these capabilities.
An example from this blog post:
I've added all workloads to my offline layout, and I've included them in my installation.
I know this is possible, because earlier I accidentally included Python and VS 2019 Build Tools in my Node.js installation configuration. The VS-related capabilities were found by the agent then.
But I'm trying to get 2022, so I uninstalled 2019.
How can I get the 2022 VS-related capabilities to be installed and detected by my build agent, without installing the full Visual Studio product?
You need to upgrade the agent to a recent enough version. You can download the agent from the azure-pipelines-agent repository's releases page. Or manually specify the capabilities.
You may need to set a special environment flag on the agent to prevent it from automatically being downgraded to whatever version shipped with your version if Azure DevOps Server or Team Foundation Server.
And then you'll also need to install the latest version of the vsbuild/msbuild and vstest tasks
Required agent version
You will need to install the most recent agent from the azure-pipelines-agent repository for it to auto-detect Visual Studio 2022, or alternatively add the capabilities to the agent manually.
You may need to force Azure DevOps Server to not downgrade back to its preferred agent version. You can do so by setting the following environment variable at the system level on your server before launching the agent:
AZP_AGENT_DOWNGRADE_DISABLED=true
These tricks will work for most tasks in the azure-pipelines-tasks repository, as long as it doesn't depend on a UI extension or service connection type that isn't available in your version of Azure DevOps Server.
https://jessehouwing.net/adding-visual-studio-2022-to-azure-devops-server-2020/

Local servicefabric cluster no longer shown in server explorer in visual studio

I just upgraded the ServiceFabric SDK to version 1.5.175. In Visual Studio (2015) I no longer see the Local cluster in the Server Explorer.
Questions:
1) How can I add the Local cluster to the Server Explorer?
2) Is there another way to see the diagnostics log in Visual Studio (or elsewhere).
Thanks,
Bart
Going forward, the best experience for interacting with Azure resources (including the Service Fabric local cluster) in Visual Studio is Cloud Explorer.
You can also bring up the diagnostic viewer from View > Other Windows > Diagnostic Events Viewer.

Visual Studio Online with local TFS 2010 Build Service

Was wondering if anyone has had success with getting a local TFS 2010 build server to perform builds for a project hosted in Visual Studio Online?
We have some legacy components (and some more recent .NET components) in our build (VB6, NSIS) and we have XP machines running TFS 2010 which can build these (we also have reasons to want to perform the build under an x86 OS).
Moving to Visual Studio Online, we had hoped to be able to keep our existing TFS 2010 build servers (or clone the VMs at least) and just point them at the cloud; however running the TFS 2010 installer and its setup wizard does not seem to work; even after installing TFS 2010 SP1 and the Visual Studio 2010 SP1 Team Foundation Server Compatibility GDR.
The problem seems to be that TFS 2010 does not recognise MSDN accounts as the credentials for the connection to TFS; I can get as far as entering the URL for our VS Cloud, selecting the project, and then proceeding through the wizard to specify the build controllers and agents, and the user the service runs under, but the verify step then fails saying that the account the build server runs under (I have tried my personal account and Network Service - MSDN accounts are refused) does not have permission within our Visual Studio Online project.
I have seen that other versions of TFS allow a separate MSDN account to be specifies for the Visual Studio Online credential, but even after installing SP1 and the hotfix this does not seem to be supported under TFS 2010.
Online searches for this have been unhelpful.
Does anyone have direct experience of this kind of setup?