#msbuild — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #msbuild, aggregated by home.social.
-
i think #cmake deserves serious recognition for making a high level abstraction over both Linux build systems, and MSVC + (!) #msbuild. i know this is one of the purposes of having a cross-platform meta-build system to begin with, but it's easy to underestimate the difficulty of getting it into a format that works with the Visual Studio toolchain. it seems waaaayyyy more involved than just getting a Clang + #Ninja project to compile on Windows.
with MSBuild, there is so much undocumented behavior to reverse engineer, concepts that don't cleanly match systems in the Makefile family. MSBuild is actually more of a declarative format with complex logic encoded in the vendored property and target files, rather than just having a self-contained set of rules. despite this, CMake seems to maintain good parity with MSBuild, e.g. with ARM64EC support
-
i think #cmake deserves serious recognition for making a high level abstraction over both Linux build systems, and MSVC + (!) #msbuild. i know this is one of the purposes of having a cross-platform meta-build system to begin with, but it's easy to underestimate the difficulty of getting it into a format that works with the Visual Studio toolchain. it seems waaaayyyy more involved than just getting a Clang + #Ninja project to compile on Windows.
with MSBuild, there is so much undocumented behavior to reverse engineer, concepts that don't cleanly match systems in the Makefile family. MSBuild is actually more of a declarative format with complex logic encoded in the vendored property and target files, rather than just having a self-contained set of rules. despite this, CMake seems to maintain good parity with MSBuild, e.g. with ARM64EC support
-
i think #cmake deserves serious recognition for making a high level abstraction over both Linux build systems, and MSVC + (!) #msbuild. i know this is one of the purposes of having a cross-platform meta-build system to begin with, but it's easy to underestimate the difficulty of getting it into a format that works with the Visual Studio toolchain. it seems waaaayyyy more involved than just getting a Clang + #Ninja project to compile on Windows.
with MSBuild, there is so much undocumented behavior to reverse engineer, concepts that don't cleanly match systems in the Makefile family. MSBuild is actually more of a declarative format with complex logic encoded in the vendored property and target files, rather than just having a self-contained set of rules. despite this, CMake seems to maintain good parity with MSBuild, e.g. with ARM64EC support
-
i think #cmake deserves serious recognition for making a high level abstraction over both Linux build systems, and MSVC + (!) #msbuild. i know this is one of the purposes of having a cross-platform meta-build system to begin with, but it's easy to underestimate the difficulty of getting it into a format that works with the Visual Studio toolchain. it seems waaaayyyy more involved than just getting a Clang + #Ninja project to compile on Windows.
with MSBuild, there is so much undocumented behavior to reverse engineer, concepts that don't cleanly match systems in the Makefile family. MSBuild is actually more of a declarative format with complex logic encoded in the vendored property and target files, rather than just having a self-contained set of rules. despite this, CMake seems to maintain good parity with MSBuild, e.g. with ARM64EC support
-
i think #cmake deserves serious recognition for making a high level abstraction over both Linux build systems, and MSVC + (!) #msbuild. i know this is one of the purposes of having a cross-platform meta-build system to begin with, but it's easy to underestimate the difficulty of getting it into a format that works with the Visual Studio toolchain. it seems waaaayyyy more involved than just getting a Clang + #Ninja project to compile on Windows.
with MSBuild, there is so much undocumented behavior to reverse engineer, concepts that don't cleanly match systems in the Makefile family. MSBuild is actually more of a declarative format with complex logic encoded in the vendored property and target files, rather than just having a self-contained set of rules. despite this, CMake seems to maintain good parity with MSBuild, e.g. with ARM64EC support
-
From the .NET blog...
In case you missed it earlier...
Analyze MSBuild Binary Logs with Copilot in VS Code
https://devblogs.microsoft.com/dotnet/msbuild-binlog-analyzer-vscode/ #dotnet #AI #VisualStudioCode #binlog #builddiagnostics #BuildPerformance #GitHubCopilot #MCP #ModelContextProtocol #msbuild #VSCode -
From the .NET blog...
In case you missed it earlier...
Analyze MSBuild Binary Logs with Copilot in VS Code
https://devblogs.microsoft.com/dotnet/msbuild-binlog-analyzer-vscode/ #dotnet #AI #VisualStudioCode #binlog #builddiagnostics #BuildPerformance #GitHubCopilot #MCP #ModelContextProtocol #msbuild #VSCode -
From the .NET blog...
In case you missed it earlier...
Analyze MSBuild Binary Logs with Copilot in VS Code
https://devblogs.microsoft.com/dotnet/msbuild-binlog-analyzer-vscode/ #dotnet #AI #VisualStudioCode #binlog #builddiagnostics #BuildPerformance #GitHubCopilot #MCP #ModelContextProtocol #msbuild #VSCode -
From the .NET blog...
In case you missed it earlier...
Analyze MSBuild Binary Logs with Copilot in VS Code
https://devblogs.microsoft.com/dotnet/msbuild-binlog-analyzer-vscode/ #dotnet #AI #VisualStudioCode #binlog #builddiagnostics #BuildPerformance #GitHubCopilot #MCP #ModelContextProtocol #msbuild #VSCode -
From the .NET blog...
In case you missed it earlier...
Analyze MSBuild Binary Logs with Copilot in VS Code
https://devblogs.microsoft.com/dotnet/msbuild-binlog-analyzer-vscode/ #dotnet #AI #VisualStudioCode #binlog #builddiagnostics #BuildPerformance #GitHubCopilot #MCP #ModelContextProtocol #msbuild #VSCode -
via @dotnet : Analyze MSBuild Binary Logs with Copilot in VS Code
https://ift.tt/7HjkrhP
#MSBuild #BinlogAnalyzer #VSCode #Copilot #GitHubCopilotChat #BinaryLogs #MSBuildLogs #CI_CD #BuildAnalysis #Performance #BuildTimeline #BuildOptimization #IncrementalBuild … -
via @dotnet : Analyze MSBuild Binary Logs with Copilot in VS Code
https://ift.tt/7HjkrhP
#MSBuild #BinlogAnalyzer #VSCode #Copilot #GitHubCopilotChat #BinaryLogs #MSBuildLogs #CI_CD #BuildAnalysis #Performance #BuildTimeline #BuildOptimization #IncrementalBuild … -
via @dotnet : Analyze MSBuild Binary Logs with Copilot in VS Code
https://ift.tt/7HjkrhP
#MSBuild #BinlogAnalyzer #VSCode #Copilot #GitHubCopilotChat #BinaryLogs #MSBuildLogs #CI_CD #BuildAnalysis #Performance #BuildTimeline #BuildOptimization #IncrementalBuild … -
via @dotnet : Analyze MSBuild Binary Logs with Copilot in VS Code
https://ift.tt/7HjkrhP
#MSBuild #BinlogAnalyzer #VSCode #Copilot #GitHubCopilotChat #BinaryLogs #MSBuildLogs #CI_CD #BuildAnalysis #Performance #BuildTimeline #BuildOptimization #IncrementalBuild … -
via @dotnet : Analyze MSBuild Binary Logs with Copilot in VS Code
https://ift.tt/7HjkrhP
#MSBuild #BinlogAnalyzer #VSCode #Copilot #GitHubCopilotChat #BinaryLogs #MSBuildLogs #CI_CD #BuildAnalysis #Performance #BuildTimeline #BuildOptimization #IncrementalBuild … -
Analyze MSBuild Binary Logs with Copilot in VS Code
https://devblogs.microsoft.com/dotnet/msbuild-binlog-analyzer-vscode/#microsoft #NET #AI #Visual_Studio_Code #binlog #build_diagnostics #Build_Performance #GitHub_Copilot #MCP #Model_Context_Protocol #msbuild #VS_Code
-
Analyze MSBuild Binary Logs with Copilot in VS Code
https://devblogs.microsoft.com/dotnet/msbuild-binlog-analyzer-vscode/#microsoft #NET #AI #Visual_Studio_Code #binlog #build_diagnostics #Build_Performance #GitHub_Copilot #MCP #Model_Context_Protocol #msbuild #VS_Code
-
Analyze MSBuild Binary Logs with Copilot in VS Code
https://devblogs.microsoft.com/dotnet/msbuild-binlog-analyzer-vscode/#microsoft #NET #AI #Visual_Studio_Code #binlog #build_diagnostics #Build_Performance #GitHub_Copilot #MCP #Model_Context_Protocol #msbuild #VS_Code
-
From the .NET blog...
Analyze MSBuild Binary Logs with Copilot in VS Code
https://devblogs.microsoft.com/dotnet/msbuild-binlog-analyzer-vscode/ #dotnet #AI #VisualStudioCode #binlog #builddiagnostics #BuildPerformance #GitHubCopilot #MCP #ModelContextProtocol #msbuild #VSCode -
From the .NET blog...
Analyze MSBuild Binary Logs with Copilot in VS Code
https://devblogs.microsoft.com/dotnet/msbuild-binlog-analyzer-vscode/ #dotnet #AI #VisualStudioCode #binlog #builddiagnostics #BuildPerformance #GitHubCopilot #MCP #ModelContextProtocol #msbuild #VSCode -
From the .NET blog...
Analyze MSBuild Binary Logs with Copilot in VS Code
https://devblogs.microsoft.com/dotnet/msbuild-binlog-analyzer-vscode/ #dotnet #AI #VisualStudioCode #binlog #builddiagnostics #BuildPerformance #GitHubCopilot #MCP #ModelContextProtocol #msbuild #VSCode -
From the .NET blog...
Analyze MSBuild Binary Logs with Copilot in VS Code
https://devblogs.microsoft.com/dotnet/msbuild-binlog-analyzer-vscode/ #dotnet #AI #VisualStudioCode #binlog #builddiagnostics #BuildPerformance #GitHubCopilot #MCP #ModelContextProtocol #msbuild #VSCode -
From the .NET blog...
Analyze MSBuild Binary Logs with Copilot in VS Code
https://devblogs.microsoft.com/dotnet/msbuild-binlog-analyzer-vscode/ #dotnet #AI #VisualStudioCode #binlog #builddiagnostics #BuildPerformance #GitHubCopilot #MCP #ModelContextProtocol #msbuild #VSCode -
Malwarebytes finds fake games spreading Amatera Stealer through RenPy Loader, MSBuild abuse, and EtherHiding C2. See the infection chain and defenses.
#RenPyLoader #AmateraStealer #EtherHiding #MSBuild #Infostealer #Malware #GamingSecurity #Malwarebytes
-
Malwarebytes finds fake games spreading Amatera Stealer through RenPy Loader, MSBuild abuse, and EtherHiding C2. See the infection chain and defenses.
#RenPyLoader #AmateraStealer #EtherHiding #MSBuild #Infostealer #Malware #GamingSecurity #Malwarebytes
-
MSBuild binlog viewer downloads have fallen off the cliff since ~March:
My interpretation is that AI is solving MSBuild issues, as well as less and less people using MSBuild. Also hopefully modern MSBuild and SDK is more pit of success.
-
MSBuild binlog viewer downloads have fallen off the cliff since ~March:
My interpretation is that AI is solving MSBuild issues, as well as less and less people using MSBuild. Also hopefully modern MSBuild and SDK is more pit of success.
-
MSBuild binlog viewer downloads have fallen off the cliff since ~March:
My interpretation is that AI is solving MSBuild issues, as well as less and less people using MSBuild. Also hopefully modern MSBuild and SDK is more pit of success.
-
MSBuild binlog viewer downloads have fallen off the cliff since ~March:
My interpretation is that AI is solving MSBuild issues, as well as less and less people using MSBuild. Also hopefully modern MSBuild and SDK is more pit of success.
-
MSBuild binlog viewer downloads have fallen off the cliff since ~March:
My interpretation is that AI is solving MSBuild issues, as well as less and less people using MSBuild. Also hopefully modern MSBuild and SDK is more pit of success.
-
Over at @InfoWorld I took a look at some of the new developer tooling for Windows that Microsoft announced back at #msbuild: support for UNIX coreutils in Windows and new ways to quickly set up and manage developer workstations.
https://www.infoworld.com/article/4188967/making-windows-a-developer-platform-again.html
-
Over at @InfoWorld I took a look at some of the new developer tooling for Windows that Microsoft announced back at #msbuild: support for UNIX coreutils in Windows and new ways to quickly set up and manage developer workstations.
https://www.infoworld.com/article/4188967/making-windows-a-developer-platform-again.html
-
Over at @InfoWorld I took a look at some of the new developer tooling for Windows that Microsoft announced back at #msbuild: support for UNIX coreutils in Windows and new ways to quickly set up and manage developer workstations.
https://www.infoworld.com/article/4188967/making-windows-a-developer-platform-again.html
-
Over at @InfoWorld I took a look at some of the new developer tooling for Windows that Microsoft announced back at #msbuild: support for UNIX coreutils in Windows and new ways to quickly set up and manage developer workstations.
https://www.infoworld.com/article/4188967/making-windows-a-developer-platform-again.html
-
Over at @InfoWorld I took a look at some of the new developer tooling for Windows that Microsoft announced back at #msbuild: support for UNIX coreutils in Windows and new ways to quickly set up and manage developer workstations.
https://www.infoworld.com/article/4188967/making-windows-a-developer-platform-again.html
-
via @dotnet : MCP Beyond the Chat Window: Build Diagnostics in CI
https://ift.tt/azRNoku
#mcp #binlog #ci #githubactions #dotnet #msbuild #diagnostics #binlogtools #buildfailureanalysis #prcomments #automation #aiassistance #continuousintegration #binlogserver #… -
via @dotnet : MCP Beyond the Chat Window: Build Diagnostics in CI
https://ift.tt/azRNoku
#mcp #binlog #ci #githubactions #dotnet #msbuild #diagnostics #binlogtools #buildfailureanalysis #prcomments #automation #aiassistance #continuousintegration #binlogserver #… -
via @dotnet : MCP Beyond the Chat Window: Build Diagnostics in CI
https://ift.tt/azRNoku
#mcp #binlog #ci #githubactions #dotnet #msbuild #diagnostics #binlogtools #buildfailureanalysis #prcomments #automation #aiassistance #continuousintegration #binlogserver #… -
via @dotnet : MCP Beyond the Chat Window: Build Diagnostics in CI
https://ift.tt/azRNoku
#mcp #binlog #ci #githubactions #dotnet #msbuild #diagnostics #binlogtools #buildfailureanalysis #prcomments #automation #aiassistance #continuousintegration #binlogserver #… -
via @dotnet : MCP Beyond the Chat Window: Build Diagnostics in CI
https://ift.tt/azRNoku
#mcp #binlog #ci #githubactions #dotnet #msbuild #diagnostics #binlogtools #buildfailureanalysis #prcomments #automation #aiassistance #continuousintegration #binlogserver #… -
From the .NET blog...
In case you missed it earlier...
MCP Beyond the Chat Window: Build Diagnostics in CI
https://devblogs.microsoft.com/dotnet/mcp-build-diagnostics-workflows/ #dotnet #AI #binlog #builddiagnostics #GitHubActions #GitHubCopilot #MCP #MicrosoftBinlogMCP #ModelContextProtocol #msbuild -
From the .NET blog...
In case you missed it earlier...
MCP Beyond the Chat Window: Build Diagnostics in CI
https://devblogs.microsoft.com/dotnet/mcp-build-diagnostics-workflows/ #dotnet #AI #binlog #builddiagnostics #GitHubActions #GitHubCopilot #MCP #MicrosoftBinlogMCP #ModelContextProtocol #msbuild -
From the .NET blog...
In case you missed it earlier...
MCP Beyond the Chat Window: Build Diagnostics in CI
https://devblogs.microsoft.com/dotnet/mcp-build-diagnostics-workflows/ #dotnet #AI #binlog #builddiagnostics #GitHubActions #GitHubCopilot #MCP #MicrosoftBinlogMCP #ModelContextProtocol #msbuild -
From the .NET blog...
In case you missed it earlier...
MCP Beyond the Chat Window: Build Diagnostics in CI
https://devblogs.microsoft.com/dotnet/mcp-build-diagnostics-workflows/ #dotnet #AI #binlog #builddiagnostics #GitHubActions #GitHubCopilot #MCP #MicrosoftBinlogMCP #ModelContextProtocol #msbuild -
From the .NET blog...
In case you missed it earlier...
MCP Beyond the Chat Window: Build Diagnostics in CI
https://devblogs.microsoft.com/dotnet/mcp-build-diagnostics-workflows/ #dotnet #AI #binlog #builddiagnostics #GitHubActions #GitHubCopilot #MCP #MicrosoftBinlogMCP #ModelContextProtocol #msbuild -
MCP Beyond the Chat Window: Build Diagnostics in CI
https://devblogs.microsoft.com/dotnet/mcp-build-diagnostics-workflows/#microsoft #NET #AI #binlog #build_diagnostics #GitHub_Actions #GitHub_Copilot #MCP #Microsoft_Binlog_MCP #Model_Context_Protocol #msbuild
-
MCP Beyond the Chat Window: Build Diagnostics in CI
https://devblogs.microsoft.com/dotnet/mcp-build-diagnostics-workflows/#microsoft #NET #AI #binlog #build_diagnostics #GitHub_Actions #GitHub_Copilot #MCP #Microsoft_Binlog_MCP #Model_Context_Protocol #msbuild
-
MCP Beyond the Chat Window: Build Diagnostics in CI
https://devblogs.microsoft.com/dotnet/mcp-build-diagnostics-workflows/#microsoft #NET #AI #binlog #build_diagnostics #GitHub_Actions #GitHub_Copilot #MCP #Microsoft_Binlog_MCP #Model_Context_Protocol #msbuild
-
From the .NET blog...
MCP Beyond the Chat Window: Build Diagnostics in CI
https://devblogs.microsoft.com/dotnet/mcp-build-diagnostics-workflows/ #dotnet #AI #binlog #builddiagnostics #GitHubActions #GitHubCopilot #MCP #MicrosoftBinlogMCP #ModelContextProtocol #msbuild -
From the .NET blog...
MCP Beyond the Chat Window: Build Diagnostics in CI
https://devblogs.microsoft.com/dotnet/mcp-build-diagnostics-workflows/ #dotnet #AI #binlog #builddiagnostics #GitHubActions #GitHubCopilot #MCP #MicrosoftBinlogMCP #ModelContextProtocol #msbuild -
From the .NET blog...
MCP Beyond the Chat Window: Build Diagnostics in CI
https://devblogs.microsoft.com/dotnet/mcp-build-diagnostics-workflows/ #dotnet #AI #binlog #builddiagnostics #GitHubActions #GitHubCopilot #MCP #MicrosoftBinlogMCP #ModelContextProtocol #msbuild -
From the .NET blog...
MCP Beyond the Chat Window: Build Diagnostics in CI
https://devblogs.microsoft.com/dotnet/mcp-build-diagnostics-workflows/ #dotnet #AI #binlog #builddiagnostics #GitHubActions #GitHubCopilot #MCP #MicrosoftBinlogMCP #ModelContextProtocol #msbuild -
From the .NET blog...
MCP Beyond the Chat Window: Build Diagnostics in CI
https://devblogs.microsoft.com/dotnet/mcp-build-diagnostics-workflows/ #dotnet #AI #binlog #builddiagnostics #GitHubActions #GitHubCopilot #MCP #MicrosoftBinlogMCP #ModelContextProtocol #msbuild -
From the .NET blog...
In case you missed it earlier...
AI-Powered MSBuild Investigation with the Microsoft Binlog MCP Server
https://devblogs.microsoft.com/dotnet/msbuild-binlog-mcp-server/ #dotnet #AI #binlog #builddiagnostics #GitHubCopilot #MCP #ModelContextProtocol #msbuild -
From the .NET blog...
In case you missed it earlier...
AI-Powered MSBuild Investigation with the Microsoft Binlog MCP Server
https://devblogs.microsoft.com/dotnet/msbuild-binlog-mcp-server/ #dotnet #AI #binlog #builddiagnostics #GitHubCopilot #MCP #ModelContextProtocol #msbuild -
From the .NET blog...
In case you missed it earlier...
AI-Powered MSBuild Investigation with the Microsoft Binlog MCP Server
https://devblogs.microsoft.com/dotnet/msbuild-binlog-mcp-server/ #dotnet #AI #binlog #builddiagnostics #GitHubCopilot #MCP #ModelContextProtocol #msbuild -
From the .NET blog...
In case you missed it earlier...
AI-Powered MSBuild Investigation with the Microsoft Binlog MCP Server
https://devblogs.microsoft.com/dotnet/msbuild-binlog-mcp-server/ #dotnet #AI #binlog #builddiagnostics #GitHubCopilot #MCP #ModelContextProtocol #msbuild -
From the .NET blog...
In case you missed it earlier...
AI-Powered MSBuild Investigation with the Microsoft Binlog MCP Server
https://devblogs.microsoft.com/dotnet/msbuild-binlog-mcp-server/ #dotnet #AI #binlog #builddiagnostics #GitHubCopilot #MCP #ModelContextProtocol #msbuild -
RE: https://hachyderm.io/@tmeschter/116751973349195922
There's another option for getting information out of MSBuild that I didn't cover before because the thread was getting long: `-getTargetResult`.
In MSBuild a target can (optionally) return a set of items. This lets you treat it as a function, not just a "unit of work".
For example, you can run:
`dotnet build -getTargetResult:ResolveReferences`and get
```
{
"TargetResults": {
"ResolveReferences": {
"Result": "Success",
"Items": [
{
"Identity": "C:\\Program Files\\dotnet\\packs\\Microsoft.NETCore.App.Ref\\10.0.8\\ref\\net10.0\\Microsoft.CSharp.dll",
"FileVersion": "10.0.826.23019",
...
},
{
"Identity": "C:\\Program Files\\dotnet\\packs\\Microsoft.NETCore.App.Ref\\10.0.8\\ref\\net10.0\\Microsoft.VisualBasic.Core.dll",
"FileVersion": "15.0.826.23019",
...
},
...
]
}
}
}
```
which is a list of all the references being passed to the C# compiler, along with a bunch of metadata on each.Or you can run the "Build" target and get information about the outputs:
```
> dotnet build -getTargetResult:Build
{
"TargetResults": {
"Build": {
"Result": "Success",
"Items": [
{
"Identity": "C:\\Users\\me\\source\\repos\\TestConsole\\TestConsole\\bin\\Debug\\net10.0\\TestConsole.dll",
"ReferenceAssembly": "C:\\Users\\me\\source\\repos\\TestConsole\\TestConsole\\obj\\Debug\\net10.0\\ref\\TestConsole.dll",
"FullPath": "C:\\Users\\me\\source\\repos\\TestConsole\\TestConsole\\bin\\Debug\\net10.0\\TestConsole.dll",
...
}
]
}
}
}
```So depending on the target that can be another option.
-
RE: https://hachyderm.io/@tmeschter/116751973349195922
There's another option for getting information out of MSBuild that I didn't cover before because the thread was getting long: `-getTargetResult`.
In MSBuild a target can (optionally) return a set of items. This lets you treat it as a function, not just a "unit of work".
For example, you can run:
`dotnet build -getTargetResult:ResolveReferences`and get
```
{
"TargetResults": {
"ResolveReferences": {
"Result": "Success",
"Items": [
{
"Identity": "C:\\Program Files\\dotnet\\packs\\Microsoft.NETCore.App.Ref\\10.0.8\\ref\\net10.0\\Microsoft.CSharp.dll",
"FileVersion": "10.0.826.23019",
...
},
{
"Identity": "C:\\Program Files\\dotnet\\packs\\Microsoft.NETCore.App.Ref\\10.0.8\\ref\\net10.0\\Microsoft.VisualBasic.Core.dll",
"FileVersion": "15.0.826.23019",
...
},
...
]
}
}
}
```
which is a list of all the references being passed to the C# compiler, along with a bunch of metadata on each.Or you can run the "Build" target and get information about the outputs:
```
> dotnet build -getTargetResult:Build
{
"TargetResults": {
"Build": {
"Result": "Success",
"Items": [
{
"Identity": "C:\\Users\\me\\source\\repos\\TestConsole\\TestConsole\\bin\\Debug\\net10.0\\TestConsole.dll",
"ReferenceAssembly": "C:\\Users\\me\\source\\repos\\TestConsole\\TestConsole\\obj\\Debug\\net10.0\\ref\\TestConsole.dll",
"FullPath": "C:\\Users\\me\\source\\repos\\TestConsole\\TestConsole\\bin\\Debug\\net10.0\\TestConsole.dll",
...
}
]
}
}
}
```So depending on the target that can be another option.