| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
Extend commit 46b0202ce0 (VS: Fix SLNX generation so CSharp projects
build in the IDE, 2025-10-23, v4.2.0-rc2~26^2) to cover .NET Core
projects.
Fixes: #27524
|
| |
|
|
| |
Issue: #27524
|
| |
|
|
| |
It is a NodeJS Project.
|
| |
|
|
| |
Fixes: #27505
|
| |
|
|
|
|
| |
It is a Windows Application Packaging Project.
Issue: #27392
|
| |
|
|
|
|
|
|
| |
Extend commit e6aa7742b0 (VS: Generate .slnx files for VS 2026,
2025-09-17, v4.2.0-rc1~151^2) to add the `Type=` attribute on SLNX
`<Project>` elements.
Fixes: #27392
|
| |
|
|
|
|
|
|
|
| |
At the time of commit e6aa7742b0 (VS: Generate .slnx files for VS 2026,
2025-09-17, v4.2.0-rc1~151^2), the VS 18 Insiders edition did not offer
support for specifying a default startup project in `.slnx` files.
This has since been added, so use it.
Fixes: #27387
|
| |
|
|
|
|
| |
Filter each mapping to apply only to its intended solution-wide config.
Fixes: #27385
|
| |
|
|
|
|
|
|
| |
Add an explicit solution-level per-project `Platform` for `.csproj`
projects even if it is the same as the solution-wide `Platform`.
Otherwise the VS IDE skips building it.
Fixes: #27330
|
| |
|
|
|
|
| |
Refactoring in commit 3882718872 (VS: Decouple solution generation from
`.sln` file format, 2025-09-15) accidentally left out automatic
detection of the external project type id from its file extension.
|
| |
|
|
|
|
|
|
| |
Since the `Visual Studio 18 2026` generator is new, we can switch
to the `.slnx` file format without changing behavior for users of
VS 2022 and older.
Fixes: #25887
|
|
|
Rewrite `.sln` generation using a structured intermediate representation.
Issue: #25887
|