hvanbakel/CsprojToVs2017
Tooling for converting pre 2017 project to the new Visual Studio 2017 format. observed · 2026-08-28
Health v2 · maintenance only
39/100
- Activity 36
- Release rhythm 8
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 3384
- days_rel: n/a
- days_push: 388
- n_releases_24m: 0
Adoption not part of the score
1100 stars · 118 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
A .NET global tool that converts legacy Visual Studio project files (pre-2017 csproj) to the modern SDK-style format used by VS2017/2019+. It shortens project files by using wildcards, simplified references, and inline NuGet/AssemblyInfo settings.
Use cases
- convert old csproj to new visual studio 2017 format
- migrate .net project to sdk-style csproj
- upgrade vs2015 project files to vs2019
- clean up verbose csproj with wildcard includes
- batch migrate solution projects to modern format
When to choose
- you have legacy non-SDK csproj files you want modernized
- you want smaller, cleaner project files with wildcard includes
- you need an automated, scriptable migration via dotnet tool
When to avoid
- your project is already SDK-style
- you rely on exotic legacy MSBuild features the converter may not handle
- you need a GUI-based migration
Facets
cli-tool · maturity maintenance
developer-tools build-tool developer-tools cross-platform cli windows csproj visual-studio project-migration dotnet-tool sdk-style-projects command-line
1 source
- readme: https://github.com/hvanbakel/CsprojToVs2017 · fetched 2026-08-28 · baaaa79b598b
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| hvanbakel/CsprojToVs2017 | main | 39 |
For agents
markdown · JSON · MCP: product_card(name="hvanbakel/CsprojToVs2017")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem