msbuild | Microsoft Build Engine is the build platform | Code Editor library

I have an Azure pipeline setup for my builds. I have been running into this issue recently and cannot figure out a way to fix this:

Every time I go to build any project in Visual Studio 2022, all I get in the buil output is:

In .NET, you can specify which .NET project SDK you would like to use by specifying the Sdk attribute on the top-level Project element:

I have run in to an odd problem after converting a bunch of my YAML pipelines to use templates for holding job logic as well as for defining my pipeline variables. The pipelines run perfectly fine, however I get a "Some recent issues detected related to pipeline trigger." warning at the top of the pipeline summary page and viewing details only states: "Configuring the trigger failed, edit and save the pipeline again."

The odd part here is that the pipeline works completely fine, including triggers. Nothing is broken and no further details are given about the supposed issue. I currently have YAML triggers overridden for the pipeline, but I did also define the same trigger in the YAML to see if that would help (it did not).

I'm looking for any ideas on what might be causing this or how I might be able to further troubleshoot it given the complete lack of detail that the error/warning provides. It's causing a lot of confusion among developers who think there might be a problem with their builds as a result of the warning.

Here is the main pipeline. the build repository is a shared repository for holding code that is used across multiple repos in the build system. dev.yaml contains dev environment specific variable values. Shared holds conditionally set variables based on the branch the pipeline is running on.

I'm completely new to trying to implement GitLab's CI/CD pipelines, but it's been going quite well. In fact, for my ASP.NET project, if I specify a Publish Profile in the msbuild command that uses Web Deploy, it actually deploys the code successfully to the web server.

However, I'm now wanting to have the "build" job create artifacts which are uploaded to GitLab that I can then subsequently deploy. We're using a self-hosted instance of GitLab, for which I'm not an admin, but I can speak to the admin if I know what I'm asking for!

So I've configured my gitlab-ci.yml file like this:

I'm trying to install npm install node-sass --save-dev in my windows 11 but I get this npm ERR! gyp ERR!

Error details:

I'm currently investigating migrating our toolset from VS2013, 15, and 17 to just VS2022 in order to streamline and reduce the amount of software needed to build our solution. VS2022 has all the parts we need however I'm struggling to get the actual solution to build through VS itself.

The solution builds entirely fine if I use the accompanying 32 bit version of msbuild at the path C:\Program Files\Microsoft Visual Studio\2022\Community\Msbuild\Current\Bin\MSBuild.exe. However the C:\Program Files\Microsoft Visual Studio\2022\Community\Msbuild\Current\Bin\amd64\MSBuild.exe version (which I'm guessing VS22 uses?) fails to build with the same errors as through VS22.

It's important to note our solution/projects are primarily based on .net framework 2.0 (unfortunately) and are set to x86 platform.

I keep cycling back to the following error SGEN : error : An attempt was made to load an assembly with an incorrect format on various first and third-party dll's. I've been trialling back and forth combinations of the following:

• changing projects between x86 and AnyCPU but the error still crops regardless of the project and it's references' configurations
• turning off Generate serialization assembly on the projects as I've seen somewhere that people have had success solving the error by doing this.
• changing ToolsVersion from 4.0 (our current setting) to Current and other versions

I'm effectively looking for a way to force VS2022 to use the 32bit msbuild if that's at all possible as it builds the entire solution without making any changes at all.

I did also notice the following in VS output window:

I'm attempting to scaffold the Identity pages for a new .NET 6.0 project (created from the ASP.NET Core MVC template). When I run the following command I get the error "path is empty" (I also included the build command output to show the project builds successfully).

We have a CD/CI Azure Devops build pipeline that has started failing for nodejs/node-gyp.

• error gyp info using node-gyp@3.8.0
• error gyp info using node@16.13.0 | win32 | x64

Nothing about our build pipeline has changed, the pool we use is: