-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move most of CoreLib interop under Common #1247
Conversation
Contributes to #1232
src/libraries/System.IO.FileSystem.AccessControl/src/System.IO.FileSystem.AccessControl.csproj
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it make sense for 100% of our interop files to be in this one location even if they are not shared?
Hmm, the extern declarations that aren't already in common, corelib, or tests are below. Mostly these are either not of general interest, or in legacy libraries we don't want to disturb. So not worth modifying them.
System.Data.OleDb\src\NativeMethods.cs
System.Data.OleDb\src\SafeNativeMethods.cs
System.Data.OleDb\src\UnsafeNativeMethods.cs
System.Data.SqlClient\src\Interop\SNINativeMethodWrapper.Windows.cs
System.Diagnostics.EventLog\src\System\Diagnostics\Reader\UnsafeNativeMethods.cs
System.DirectoryServices\src\Interop\SafeNativeMethods.cs
System.DirectoryServices\src\Interop\UnsafeNativeMethods.cs
System.DirectoryServices\src\System\DirectoryServices\ActiveDirectory\NativeMethods.cs
System.DirectoryServices\src\System\DirectoryServices\ActiveDirectory\UnsafeNativeMethods.cs
System.DirectoryServices.AccountManagement\src\System\DirectoryServices\AccountManagement\interopt.cs
System.DirectoryServices.Protocols\src\System\DirectoryServices\Protocols\ldap\Wldap32UnsafeMethods.cs
System.Drawing.Common\src\System\Drawing\Gdiplus.cs
System.Drawing.Common\src\System\Drawing\GdiplusNative.cs
System.Drawing.Common\src\System\Drawing\GdiplusNative.Unix.cs
System.Drawing.Common\src\System\Drawing\GdiplusNative.Windows.cs
System.Drawing.Common\src\System\Drawing\Icon.Windows.cs
System.Drawing.Common\src\System\Drawing\Image.cs
System.Drawing.Common\src\System\Drawing\LibX11Functions.cs
System.Drawing.Common\src\System\Drawing\macFunctions.cs
System.Drawing.Common\src\System\Drawing\Printing\LibcupsNative.cs
System.Drawing.Common\src\System\Drawing\UnsafeNativeMethods.cs
System.IO.Ports\src\Interop\Unix\Interop.Serial.cs
System.IO.Ports\src\Interop\Unix\Interop.Termios.cs
System.Security.Cryptography.Pkcs\src\Interop\Windows\Crypt32\Interop.CertDuplicateCertificateContext.cs
System.Security.Cryptography.X509Certificates\src\Internal\Cryptography\Pal.Windows\Native\Interop.crypt32.cs
System.Security.Cryptography.X509Certificates\src\Internal\Cryptography\Pal.Windows\Native\Interop.cryptoapi.cs
[edited to make sense]
We have several issues tracking the reformatting these (e.g. https://github.com/dotnet/corefx/issues/1739). As you have pointed out, it is not clear whether it is an improvement to have the definitions of domain specific APIs that are used just once under Common and split them into many little files. |
Contributes to #1232