how add naming conversion?

[IOL0ol1]

Many C language header files use lowercase underscore naming conventions. Automatic conversion to C# PascalCase (Upper CamelCase) is required.

[IOL0ol1]

Given the need to account for more complex scenarios, I’m wondering if we can implement a plugin mechanism that allows users to provide custom implementations, with usage similar to
ClangSharpPInvokeGenerator -plugin myplugin.dll ...

myplugin must contain an implementation of an interface similar to:

interface IPlugin
{
    CXCursor Preview(CXCursor cursor);
    CXCursor Process(CXCursor cursor);
}

[IOL0ol1]

These are probably two separate problems.As for plugins, that’s just a random idea I just came up with.

[tannergooding]

There is no mechanism to automatically do case conversion.

It is recommended that bindings be explicitly 1-to-1 with native. This helps with readability, working with the existing documentation, helps avoid bugs and other risk, etc

If you want to create something that is more "friendly" towards typical .NET conventions, it is instead recommended that you give explicit design thought into how that works. What makes sense for .NET, what types users are expected to interact with, etc. You then build a set of wrapper APIs over the underlying native bindings.

There are currently no plans to provide a way to do such automatic case conversion or allow any kind of general plugin system to ClangSharp itself.

[IOL0ol1]

@tannergooding
Here’s a practical scenario:
I’m using ClangSharpPInvokeGenerator to generate P/Invoke code for libVLC into a single file LibVLC.cs.
Unlike the layout in ClangSharp/sources/ClangSharp.Interop/clang, libVLC has a much smaller API surface, so a single-file output fits better.
I also want to add a manual wrapper layer similar to ClangSharp/sources/ClangSharp.Interop/Extensions, where I can:

• Turn C-style get/set functions into C# properties
• Expose a more idiomatic C# API

As a typical C project, libVLC uses snake_case everywhere, while PascalCase is the standard convention in C#.
The Clang project itself uses PascalCase, so its wrapper code can naturally reuse the original struct and method names.
However, directly using libVLC’s snake_case structs in C# feels unidiomatic.
But manually redefining all structs in PascalCase would defeat the purpose of automatic code generation.

[IOL0ol1]

There is no mechanism to automatically do case conversion.

It is recommended that bindings be explicitly 1-to-1 with native. This helps with readability, working with the existing documentation, helps avoid bugs and other risk, etc

If you want to create something that is more "friendly" towards typical .NET conventions, it is instead recommended that you give explicit design thought into how that works. What makes sense for .NET, what types users are expected to interact with, etc. You then build a set of wrapper APIs over the underlying native bindings.

There are currently no plans to provide a way to do such automatic case conversion or allow any kind of general plugin system to ClangSharp itself.

I don’t think I explained my use case clearly earlier, so I’d like to clarify.
ClangSharpPInvokeGenerator is an excellent tool.
I understand your point, and I’ll fork a separate branch to handle this.