WAPPROJ CSPROJ
Not possible

Convert WAPPROJ to CSPROJ

Can you convert WAPPROJ to CSPROJ?
QUICK ANSWER
Is it possible to convert WAPPROJ to CSPROJ?
No - not a direct conversion.

A .wapproj and a .csproj are two different roles in one Visual Studio solution: the .wapproj builds the MSIX package while the .csproj holds the actual C# app code. You cannot convert one into the other; instead you keep the .csproj for your code and let the .wapproj reference it. The realistic path is to open the solution and edit or recreate the projects in Visual Studio.

No direct path
Also to CSPROJ: SLN

On this page

Tested on macOS, Windows & Linux
Last verified Sep 2026

More free converters

HEIC, PNG, WEBP, MP3 and more - every tool here is free.

Open the toolbox

Why convert WAPPROJ to CSPROJ?

People land on this because both files sit side by side in a packaged desktop-app solution and look interchangeable. They are not: a .csproj defines an app's C# source, dependencies and build, while a .wapproj contains only packaging metadata (manifest, assets, dependencies) and a reference to the app project it packages. There is nothing in a .wapproj to compile into C#.

How to convert WAPPROJ to CSPROJ

Edit the C# project in Visual Studio FREE

Open the solution in Visual Studio 2022 and work in the existing .csproj for code; the .wapproj stays as the packaging wrapper that references it. Right-click the packaging project's Applications node to add the reference.

Move to single-project MSIX FREE

For a WinUI 3 / Windows App SDK app you can drop the separate .wapproj and use single-project MSIX, where packaging lives inside one .csproj with a Package.appxmanifest. Create a new Blank App, Packaged project and move your code in.

Inspect both files in a text editor FREE

Open the .wapproj and .csproj in VS Code or Notepad to see they are different MSBuild project types. This confirms there is no code to migrate, only a reference to reconnect.

About these formats

Quality & what to watch

  • A .wapproj holds no application source code, so there is nothing to "convert" into a .csproj.
  • The two projects are meant to coexist: the packaging project references the code project, not replace it.
  • The older two-project .wapproj model does not fully support the newer SDK-style .csproj format, which is a common source of build errors.

Frequently asked questions

Can I just rename .wapproj to .csproj?
No. They use different MSBuild imports and targets; renaming produces a project that will not load or build.
Where is my actual app code then?
In the .csproj (or .vcxproj) project that the .wapproj references, not in the packaging project itself.
How do I get rid of the .wapproj?
Migrate a WinUI 3 / Windows App SDK app to single-project MSIX, which folds packaging into one .csproj.
Why does adding a .wapproj break my build?
The classic packaging project has known compatibility gaps with SDK-style .csproj files; check the project reference and target framework.