Visual studio 2019 to 2022 D365 F&O

(4) Share

Report

Posted on by CU21052024-0

273

Hi All,

I’ve updated visual studio from 2019 to 2022, and I’ve changed build solution visual studio version to 2022 in pipeline. Can anyone help me if I need to change else where as I’m getting below warning when I ran pipeline

I have the same question (0)

All responses (3)

Answers (2)

Sort by

André Arnaud de Cal... 304,138 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi,

Have you updated Visual Studio on the build machine or on your development environment only?

Was this reply helpful? Yes No
Verified answer

Saif Ali Sabri 2,358 Moderator on at

Like (0)

Report
Copy link

Link copied!
🔧 Root Cause:
This indicates the build agent does not have Visual Studio 2022 (version 17.0) installed or configured correctly.

✅ Concise Solution:

Use a correct Microsoft-hosted agent that includes VS 2022:

In your pipeline YAML or classic UI, set the agent pool to:
yaml
CopyEdit
pool:
vmImage: 'windows-2022'
✅ windows-2022 comes with Visual Studio 2022 (17.x) pre-installed.

Ensure msbuildVersion is set to 17.0 (if using task-based YAML):

yaml
CopyEdit
- task: VSBuild@1
inputs:
msbuildVersion: '17.0'

If using a self-hosted agent, make sure:

Visual Studio 2022 is installed.

The build tools (MSBuild) component is selected during installation.

The VSINSTALLDIR environment variable or PATH is updated if needed.

Let me know if you're using a Microsoft-hosted agent or self-hosted agent, and I can tailor the fix further.

Was this reply helpful? Yes No
Verified answer

Navneeth Nagrajan 2,583 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi,

Suggestions:

Assuming your build pipelines are running on Azure hosted agents instead of agent pools then you can do the following:
1. For VSTS (Visual studio team services), update your Build solution step from Visual studio 2019 to Visual Studio 2022/Latest. Usually, prefer keeping it to Latest so the version conflicting warnings are avoided. VS2022 considers either 17.0 or Latest. Re-add your build solution step with the latest artifact (Visual studio biuld). Looks like you are using an older version of the Build solution artifact.

2. If you are using Azure DevOps Git update your pool step in YAML to 'windows-2022' and the vsbuild step to '17.0' or 'current'.

3. Also, as Saif highlighted check if the D365 Tools are installed on VS2022. DevTools services in your host VM is the repository to get this sorted.

Hope this helps. Happy to answer questions, if any.

Was this reply helpful? Yes No