Leave your comments here! -- Adam Nathan

This is such a great idea -- thanks Adam

..BradA (http://blogs.msdn.microsoft.com)

Echo Brad. This is an awesome idea! Thanks Adam. I have blogged it. -- Sam Gentile (http://samgentile.com/blog/)

Great idea, thanks for creating the site. However, it does have rendering problems on Mozilla (Firefox 0.8 on Win XP to be exact). The directory tree (advapi32, gdi32 etc.) is misplaced (overlaps the "Directory" label) and I can't get them to expand.

There is also IE (6.0.2800.1106.xpsp2) bug: clicking "Edit This Page" brings up error message "A runtime error has occurred... Line: 15 Error: 'ButtonBar' is undefined". Harmless but annoying.

Krzysztof Kowalczyk (http://blog.kowalczyk.info)

The fading effect is awesome, the whole experience is extremely 'organic'. This is really the future of documentation.

This is so cool! And work with Wiki has never been more enjoyable.

Great idea, thanks for setting it up!

One question: The APIs here appear to be machanically created from some other source - from things like "System.Windows.Forms.NativeMethods"? The functions are present, but not the structures and data types used in the params. Any plans to do a mechanical dump of the structures as well? The real magic of marshalling is getting the param types set up correctly, which for structures can be quite a pain.

Things like RegisterWindowClass and GetClassInfo using the WNDCLASS structure in different ways requires creating separate structures with different field types in order to satisfy the marshaller (The WndProc pointer as a raw IntPtr in some cases, or as a method pointer in other cases). I can see that the params for GetClassInfo and RegisterWindowClass do take different structure types, but those types do not appear to be documented here.

-Danny

(http://homepages.borland.com/dthorpe/blog/delphi)

You should also check out these automatically generated PInvoke stubs which covers much of the WIn32 API

(http://www.gotdotnet.com/Community/UserSamples/Details.aspx?SampleGuid=f1dd70e4-c212-4a6f-bff7-c82e34c8836f)

Cheers,

Peter Hallam

C# Compiler Dev Lead

How about a directory for the Compact Framework/coredll? - Ian Darling

This is great, but definitely needs somewhere we can define common constants and structures.

Rodney.

- Add a way to search and or highlight entries that have additional info added.

- Add a logon feature (use DotNetNuke?) to allow added posts to be tracked based on email address instead of IP address.

Charlie Kindel (http://www.kindel.com/blogs/charlie)

Some responses for the last 3 comments:

• Ian, I've added coredll, so feel free to start adding pages!
• Rodney, you can define pages for structures, etc. just like you can for functions. It might be nice to organize them differently, though...
• Charlie, I'll have to consider other means of tracking. In the meantime, it would be great if folks fill out the "Identity" text box when making edits. Also, you can click on the "Show Recent Changes" link to see the most-recently-updated pages across the site.

Thanks, everyone, for your participation! -- Adam Nathan

Very nice https://www.pinvoke.net/emoticons/regular_smile.gif But I also miss the structures, constants, etc. Would it be possible to organize the information such as the MSDN Library does instead? I believe it will be hard to find items in for example the shell32 tree when all enums, structures, interfaces etc. are added.

I'm thinking something like this instead:

Shell

  +-----Classes
  +-----Interfaces
  +-----Functions
  +-----Callback functions
  +-----Constants, Enumerations, and Flags
  +-----Structures
  +-----(Maybe more?)

Or is it possible to do this now giving a pagename such as shell32.Structures.APPBARDATA?

-- Andreas Häber

Cheers!

Guess I'll get started soon https://www.pinvoke.net/emoticons/regular_smile.gif

Ian Darling.

Dang - I think I broke kernel32.CreateFile when adding coredll.CreateFile - Ian Darling