We have on-prem Azure DevOps 2020 installed. We built a .net core 6 app in Visual Studio 2022.
However, when creating the build pipeline, VS 2022 is not showing up in the dropdown.
Has anyone faced this problem? Is MSFT supposed to release a patch that will start displaying VS 2022 in the dropdown?
Many people are running into this. No word from MS yet on when or if an update will be available. But these articles may help you find a workaround:
How do I update my Azure DevOps on-premise Pipeline tasks to include MSBuild v17 and Visual Studio 2022?
https://jessehouwing.net/adding-visual-studio-2022-to-azure-devops-server-2020/
https://github.com/microsoft/azure-pipelines-agent/issues/3662
FWIW, I'm working around it by using an explicit MSBuild path as mentioned in this answer. I added a PreferredMSBuildExePath variable to my pipeline and set it equal to %ProgramFiles%\Microsoft Visual Studio\2022\Professional\MSBuild\Current\Bin\amd64\MSBuild.exe. Then I made all my MSBuild steps use $(PreferredMSBuildExePath) as their MSBuild path under Specify Location. I also converted all my Visual Studio steps to MSBuild steps so I could use this explicit path variable.
Related
I have installed the SSAS extension in Visual Studio 2022, it works well but it allows me to create Multidimensional projects only. "Analysis Services Tabular Project" is missing from the list. Any idea what's going on?
Thank you
You need to install it from the Visual Studio Gallery. It looks like there is a temporary workaround in the Q&A tab to resolve the issue you are seeing.
Uninstall AS extension.
install the AS extension and close the VS2022.
copy/replace the manifest file(link to download the file is below) in the SSAS folder, a location where your VS22 is installed. For
example "C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\IDE\CommonExtensions\Microsoft\SSAS".
run the following command in cmd at a location where VS2022 is installed. For example "C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\IDE" command: "devenv.exe /updateconfiguration"
open visual studio and it should work fine.
if it still doesn't, make sure the AS extension is enabled and then execute the 3rd step again after closing VS.
link:
https://microsoftapc-my.sharepoint.com/:u:/g/personal/namangupta_microsoft_com/EdG1BxmX0W5OlLt4CHIZJqYB-8fXSocUi-zK5lqqBLURpg?e=rHCh9F
By Microsoft 3 hours ago
If you are looking for other extensions in 2022 this page has instructions and links.
Had the same problem with a old VS 2022 Version. Updating my VS 2022 to 17.3.4 an re-installing SSAS Extension was resolving the issue.
We now have a permanent fix for the issues. Please go ahead and update
your VS 2022 version to 17.2.5. You should now be able use Tabular and
Multidimensional Models.
I just migrated from SSDT 2015 to SSDT 2019 and tried to open a project created in SSDT 2015. One of the packages has a data flow task with a script component in it. The script component fails to build with the error:
Could not find part of the path
'C:\Users\xxxxxx\AppData\Local\Temp\2\Vsta\c2e811fdc5974e2ca3f7cb5426c82033_out'
I tried to delete the .vs folder in my project but that didn't work. The script still fails to rebuild. The script has a lot of classes in it so I'd rather not start from scratch and copy everything into it. Any idea what could be wrong?
Appears this issue may be caused by an incompatibility between Visual Studio 16.9 and SQL Server Integration Services Projects. The issue is described here: https://marketplace.visualstudio.com/items?itemName=SSIS.SqlServerIntegrationServicesProjects
Recommendation is to regress back to Visual Studio 16.8 or earlier.
The new version of data tools fixed it for me without rolling back to 16.8. This was a difficult issue to resolve. Nowhere in the MS documentation do they mention the tools update fixes that specific error. Thanks for the link!
I tried to open a .Net Core solution which was working fine in 2015. Recently they added some .Net Core projects to the solution and asked us to upgrade to Visual Studio 2017 to be able to run them. We installed Visual Studio 2017 and tried to open the solution, but I am not able to build it. I get the following errors when I right-click and try to select "Manage Nuget packages".
I tried to open the PackageManager console from Tools: even this is not working
I also performed the "repair Visual Studio" process too.
Finally i resolved it by deleting my nuget.config both at project level and also in %appdata%/roaming/nuget .I think the issue is because of broken config file due to change from visual 2015 to visual studio 2017 .Not sure about the exact issue though
I'm wondering if someone could help me out with this issue please.
First up the background, we've been using TeamCity for database deployments for a while. Today we upgraded to 10.0.5. All fine.
The issue we have is with SQL 2016 database projects. I'm trying to get the database project to build in TeamCity. The build 'Visual Studio' setting in the build was set to 'Microsoft Visual Studio 2015' this causes issues as it cant build it. So I changed it to be 'Microsoft Visual Studio 2017' and I installed 'Build Tools for Visual Studio 2017' on the TeamCity box.
Now when I click the run button I get a message back saying
"Warning no enabled compatible build agents......".
Its almost as if the build agent is allowed to use the VS2015 MSBuild but not the 2017 one and I'm not sure how to authorise it to be able to.
I've attached some screenshots of the screens as well.
Thanks,
Nic
I managed to resolve this simply be restarting the server.
Thanks,
Nic
We have a build definition in TFS 2015 that have worked fine with Visual Studio 2015 projects and solutions. We have now decided to upgrade to Visual Studio 2017 and thus we would like to target Visual Studio 2017 in the Visual Studio build task. We have installed Visual Studio 2017 on the build agent. Unfortunately the only options available int the Visual Studio build task are 2012, 2013, 2015 and Latest. We have tried latest but it does not find Visual Studio 2017 on the build agent. It won't work with the msbuild task either.
I have a similiar issue and resolved by installing VS2017 in my build agent server and configuring MSBuild to point to my MSBuild 15.0 folder:
Add MSBuild to your build steps
On the Advanced options, expand and fill the 'Path to MSBuild' like the image below:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin
VS2017 RTM is released recently while TFS2015 was released before. That's why there is no VS2017 option in VS Build Task in TFS2015 Server. If you upgrade your server to the latest TFS2017, you would see "Visual Studio "15" (preview)" option listed in VS Build Task which is the version for VS2017 preview. And in the feature, the option will be updated to VS2017 which is the same as VSTS.
we are facing a similar issue and it is not possible for us to update ourselves as it is maintained on a company level where we cannot take that much influence.
However our team wanted to switch to VS2017 and make use of the C# 7 features. That's why we tried it as well with replacing the build steps from Visual Studio Build to MSBuild. Sadly this did not work as expected (we got some errors during the build).
As our main objective is to use the C# 7 features we looked for a way how to still achieve that at the time with Visual Studio 2015 remaining on the Build Server. We ended up using the nuget package Microsoft.Net.Compilers that, when used in a project, will use that compiler instead of the installed one.
More on this can be found in this Thread.
It seems the updates to the build tools are installed via the command line of the VS2017 installer.
See the docs for details.
Just adding another thing: if you're using custom build template make sure to edit it and modify the ToolPath attribute value to:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin