hvanbakel/CsprojToVs2017
Tooling for converting pre 2017 project to the new Visual Studio 2017 format.
Join the conversation
Reviews · Questions · Posts
Share what you know about CsprojToVs2017 — write a review from your real experience, ask an implementation question, or publish a post about how you use it.
Share your experience
Write or update your review
Explain what worked, what broke down, and what another team should know before adopting CsprojToVs2017.
Project Q&A
Questions and answers
Browse implementation threads tied directly to hvanbakel/CsprojToVs2017. Each question links through to the full answer page.
Be the first to ask how teams run CsprojToVs2017 in production. Every question you post becomes a durable, searchable answer page other developers can find.
Ask the first questionRelated posts
Posts tagged with the same topics
These posts come from the same topic surface as this repo, so readers can move from project evaluation into practical writeups and migration notes without leaving context.
Share how your team uses CsprojToVs2017 — a migration note, an architecture writeup, or a comparison. Your post reaches everyone browsing these same topics.
Write the first post