CODEWITHSUNDEEP
c#.netpinvokenative-methods
Bryan
Bryan

Reputation: 2791

Is the class NativeMethods handled specially in .NET?

https://msdn.microsoft.com/en-us/library/ms182161.aspx

Are the three classes described on this paged handled specially in the .NET Framework? (NativeMethods, SafeNativeMethods and UnsafeNativeMethods)

The reason I'm asking is I'm wondering if it is alright to create categories of NativeMethods classes. For example:

ComNativeMethods
User32NativeMethods
OleStorageNativeMethods

Upvotes: 10

Views: 11792

Answers (4)

Ed Greaves
Ed Greaves

Reputation: 4937

You can name your classes that way, but you will continue to get the code analysis warning CA1060. This warning indicates you are not following the convention. So to prevent this warning, you need to follow the convention when naming classes that have P/Invoke methods. If you want to categorize your P/Invoke methods, you can use namespaces. For example:

  • MyProject.Com.NativeMethods
  • MyProject.User32.NativeMethods
  • MyProject.OleStorage.NativeMethods

Upvotes: 2

Pete OHanlon
Pete OHanlon

Reputation: 9146

It's a convention, not a requirement. If you reflect into the CLR and take a look at code in there, you'll often see P/Invoke code inside a NativeMethods class. I believe that FxCop will recommend putting your P/Invoke code in a class like this if it encounters it.

Upvotes: 8

Thomas Levesque
Thomas Levesque

Reputation: 292615

It's just a convention that says you should place p/invoke methods in classes named *NativeMethods, but there is no technical constraint to prevent you from doing it your own way...

Upvotes: 3

Judah Gabriel Himango
Judah Gabriel Himango

Reputation: 60041

They aren't handled specially by the CLR. It's simply recommended practice to have your P/Invokes inside a class named NativeMethods, SafeNativeMethods, or UnsafeNativeMethods.

You'll see this recommendation come into play if you run FxCop on your assemblies.

Upvotes: 1

Related Questions