Share via

Need multi-page, in-flow project creation wizard for custom template in VS 2022 (change “Create” to “Next”)

Ajay Gera 50 Reputation points
2026-03-30T16:39:07.8366667+00:00

Hi All,

I want to create a custom project template (e.g., myProjectTemplate) that users can choose in Visual Studio 2022 via File → New → Project, and I need a multi-page wizard that feels fully integrated into the standard project-creation flow.

The desired flow is:

  • The user selects myProjectTemplate and clicks Next.
  • The next screen is the standard “Configure your project” page (like the one shown for Console App (.NET Framework)). By default, it has Back and Create, but I want to change Create to Next.
  • When the user clicks Next, I want to show multiple additional pages, one after another, each with Back and Next.

I tried using .vstemplate + IWizard, but that launches wizard pages as modal dialogs on top of the existing “Configure your project” page. Instead, I want each step to be a separate page within the same wizard flow, not stacked dialogs.

How can I achieve this?

Developer technologies | Visual Studio | Extensions
0 comments No comments

3 answers

Sort by: Most helpful
  1. Susmitha T (INFOSYS LIMITED) 2,690 Reputation points Microsoft External Staff
    2026-03-31T06:50:05.5833333+00:00

    Thank you for reaching out!

     
    After reviewing your scenario, I'd like to clarify an important platform limitation in visual studio 2022: Currently, the project template system (.vstemplate with IWizard ) does not support extending or modifying the built-in "Create new project" flow. Specifically, it is not possible to:

    • Replace the "Create" button with the "Next".
    • Insert additional wizard pages into the native project's creation UI.
    • Maintain a fully in-flow, multi-page wizard experience within the standard dialog.

    This is by design, which is why your current implementation shows wizard steps as model dialogs.

    Recommended Approach: To achieve a smooth multi-step experience, we suggest the following supported pattern:

    • Allow the user to proceed with the standard flow (Template ->Configure ->Create)
    • After the user clicks Create, launch a custom multi-page wizard (e.g., WPF-based on your IWizard implementation.
    • Collect all additional inputs through this wizard and apply them during project generation.

    This approach is widely used and ensures:

    • Compatibility with Visual Studio updates
    • A clean and controlled user experience
    • Flexibility for adding multiple steps (Back/Next navigation)

     

    Alternative (Advance): If a fully integrated, in-flow wizard experience is required, this would involve developing a Visual Studio Extension (VSIX) with a custom project system. Please note that this is a more complex approach and typically used for advance scenarios.

     

    Let me know if you need any further help with this. I will be happy to assist.
    If you find this helpful, Kindly mark the provided solution as "Accept Answer", so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    1 person found this answer helpful.

  2. Ajay Gera 50 Reputation points
    2026-03-31T05:55:02.44+00:00

    For VS2022 , can my question addressed by any Nuget package?

    Is this possible for VS2026?

    1 person found this answer helpful.
    0 comments No comments

  3. Q&A Assist
    2026-03-30T16:39:24.1266667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    This cannot be done with current Visual Studio project template infrastructure.

    Visual Studio supports two main customization points for project creation templates:

    1. Template parameters and .vstemplate metadata
      These let a template participate in the normal File → New → Project flow and the standard Configure your project page, but only for simple parameter substitution (for example $safeprojectname$, custom parameters, multi‑project templates, etc.). They do not allow replacing or extending the built‑in wizard pages or changing the Create button to Next.
    2. Custom wizards via IWizard
      Implementing IWizard and wiring it in the .vstemplate lets a template run custom code and show UI when a project is created. As documented, this wizard UI is invoked from the template and typically appears as separate modal dialogs. It can:
      • Collect user input (for example via a WinForms dialog) in RunStarted.
      • Add or modify files.
      • Inject custom parameters into the template’s parameter dictionary so they replace tokens like $custommessage$ in the generated project.
      However, IWizard does not integrate into the Visual Studio “New Project” wizard as extra pages. It cannot:
      • Replace the built‑in Configure your project page.
      • Change the Create button text to Next.
      • Insert additional in‑flow pages into the same wizard frame.

    The official guidance for “customizing the wizards that create projects from templates” is exactly this IWizard mechanism, which is limited to running custom logic and UI around template processing, not reshaping the Visual Studio New Project experience into a multi‑page, in‑frame wizard.

    So with the supported APIs:

    • A multi‑page wizard can be implemented as a sequence of dialogs in an IWizard implementation.
    • A fully integrated, multi‑page, in‑flow wizard that replaces or extends the built‑in New Project pages and changes Create to Next is not supported.

    References:

    1 person found this answer helpful.
    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.