Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / New Users / October 2004

Tip: Looking for answers? Try searching our database.

Windows message -> .NET method

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Edward Diener - 04 Oct 2004 16:08 GMT
Microsoft has put out a document relating Win32 API calls to .NET methods
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/h
tml/win32map.asp ) . An equally valuable document, esspecially from the
component developer point of view, would map Windows messages to .NET
methods.

Has anyone seen such a document ?

I find myself pretty consistently looking at Win32 code which does a
SendMessage or PostMessage and searching for the .NET method which is
equivalent. Sometimes I find a method which looks like it will do what I
want, but the MSDN .NET framework documentation is often not clear enough to
tell me if it is so. Of course I can experiment, but I hate top spend time
playing arouind when a good document would already tell me.

Am I the only .NET developer who feels a need for such a document from
Microsoft to aid in porting Win32 functionality to .NET ?
Joshua Frank - 26 Oct 2004 18:38 GMT
Better still would be a Win32 namespace that actually encapsulated the
whole API in a managed way.

> Microsoft has put out a document relating Win32 API calls to .NET methods
> (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/h
[quoted text clipped - 13 lines]
> Am I the only .NET developer who feels a need for such a document from
> Microsoft to aid in porting Win32 functionality to .NET ?
Jeff Gaines - 26 Oct 2004 19:08 GMT
> Better still would be a Win32 namespace that actually encapsulated
> the whole API in a managed way.

Yes, yes yes!!!

I guess the chances are between zero and none :-)

Signature

Jeff Gaines Damerham Hampshire UK

Edward Diener - 26 Oct 2004 19:36 GMT
> Better still would be a Win32 namespace that actually encapsulated the
> whole API in a managed way.

I do not know if it would be better, since I still would not get the benefit
of knowing how Windows messages translate into .NET events. It would be
helpful so that one would not have to #include <windows.h> in VC++, use IJW,
and create mixed mode assemblies that way with their current destructive
bugginess, and of course it would be better for all languages not to have to
use InterOp just to drop to the Windows API level. But if MS documented the
messages -> .NET events better, I might not have to ever go the Win32 API
route anymore in the first place.

>> Microsoft has put out a document relating Win32 API calls to .NET
>> methods

(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/h
>> tml/win32map.asp ) . An equally valuable document, esspecially from
>> the component developer point of view, would map Windows messages to
[quoted text clipped - 12 lines]
>> Am I the only .NET developer who feels a need for such a document
>> from Microsoft to aid in porting Win32 functionality to .NET ?

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.