Skip to content

Add appmanifest config option for dotnet projects - #2769

Open
CapeGuyBen wants to merge 1 commit into
premake:masterfrom
CapeGuyGames:feature/dotnet_app_manifest
Open

Add appmanifest config option for dotnet projects#2769
CapeGuyBen wants to merge 1 commit into
premake:masterfrom
CapeGuyGames:feature/dotnet_app_manifest

Conversation

@CapeGuyBen

Copy link
Copy Markdown
Contributor

What does this PR do?

Adds an appmanifest config option for adding an <ApplicationManifest> properties to dotnet projects.

Resolves Issue 622.

How does this PR change Premake's behavior?

You can now add <ApplicationManifest> properties to dotnet projects

Did you check all the boxes?

  • Focus on a single fix or feature; remove any unrelated formatting or code changes
  • Add unit tests showing fix or feature works; all tests pass
  • Mention any related issues (put closes #XXXX in comment to auto-close issue when PR is merged)
  • Follow our coding conventions
  • Minimize the number of commits
  • Align documentation to your changes

@CapeGuyBen CapeGuyBen changed the title Add appmanifest config option Add appmanifest config option for dotnet projects Aug 12, 2026
Comment thread modules/vstudio/vs2005_dotnetbase.lua Outdated

function dotnetbase.netcore.appManifest(cfg)
if cfg.appmanifest and string.len(cfg.appmanifest) > 0 then
_p(2,'<ApplicationManifest>%s</ApplicationManifest>', cfg.appmanifest)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To which path should it be relative?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's relative to the generated .csproj

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Paths are entered relative to premake5.lua, so a path.getrelative seems missing here.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense. Added.

@CapeGuyBen
CapeGuyBen force-pushed the feature/dotnet_app_manifest branch from d478f16 to a7ccd46 Compare August 14, 2026 14:17

## Applies To ###

.Net project configurations.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should be consistent. .NET or dotnet

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Specifying application manifest file in C# project...

3 participants