Skip to main content
gamedev.net
🔒 Locked

.NET Framework

Started by CpMan 10 replies 500+ views
Original Post
CpMan
CpMan
This is to anyone who has used the .NET Framework: Is the new API designed/can be used, to completely replace calls to the traditional Windows API? Reality is Relative -Me and Probably somebody else
VSEDebug Visual Studio.NET Add-In. Enhances debugging in ways never thought possible.
thona
thona
Yes.

No.

Ok, realistically - no. You will still want to use a lot of COM objects that are not part of the framework.

For Win32 stuff, most is in there - some stuff is even there not part of the framework, like RAS or so.

Anyhow, you can basically call most dll functions without more than a handfull of declarations.
Go for it - you will nver look back.


Regards

Thomas Tomiczek
THONA Consulting Ltd.
(Microsoft MVP C#/.NET)
RegardsThomas TomiczekTHONA Consulting Ltd.(Microsoft MVP C#/.NET)
CpMan
CpMan
Really? Is it that good? What I''m basically wondering (though I''m going to find out firsthand when I get back from class today), is whether I can replace my Win32 application initialization code (window creation, message handling), with .NET framework calls, and whether it is actually worth it.

Reality is Relative -Me and Probably somebody else
VSEDebug Visual Studio.NET Add-In. Enhances debugging in ways never thought possible.
Arild Fines
Arild Fines
quote:
Original post by CpMan whether I can replace my Win32 application initialization code (window creation, message handling)

You don''t really have to:

  
using System.Windows.Forms;
public class SomeBleh
{
public static void Main()
{
Application.Run( new Form() );
}
}

That''s your run of the mill, do-nothing window.



The world holds two classes of men -- intelligent men without religion, and religious men without intelligence. - Abu''l-Ala-Al-Ma''arri (973-1057; Syrian poet)
--AnkhSVN - A Visual Studio .NET Addin for the Subversion version control system.[Project site] [IRC channel] [Blog]
CpMan
CpMan
Nice.....that''s C# though right?
VSEDebug Visual Studio.NET Add-In. Enhances debugging in ways never thought possible.
Arild Fines
Arild Fines
Yes - would be almost identical in MC++ and pretty similar in VB.NET, though.



The world holds two classes of men -- intelligent men without religion, and religious men without intelligence. - Abu''l-Ala-Al-Ma''arri (973-1057; Syrian poet)
--AnkhSVN - A Visual Studio .NET Addin for the Subversion version control system.[Project site] [IRC channel] [Blog]
CpMan
CpMan
Yeah, would be. I''m looking forward to working with the API (even though it will only serve as the base for a DirectX Application). Looks like a BIG step over the Win32 API.
VSEDebug Visual Studio.NET Add-In. Enhances debugging in ways never thought possible.
daerid
daerid
That''s the great thing about MC++: You can intersperse unmanaged C++ along with it.
daerid@gmail.com
CpMan
CpMan
On the other hand.....maybe not. You have to pass the parent window to directx initialization functions, and I can''t find a way to GET this HWND from the .NET Framework. Anyone know what the class/namespace for this is?
VSEDebug Visual Studio.NET Add-In. Enhances debugging in ways never thought possible.
CpMan
CpMan
Never Mind....found it.....deep within the class structure. It really is useful to have a class hierarchy diagram to see. The .NET Frame work is Massive.

Reality is Relative -Me and Probably somebody else
VSEDebug Visual Studio.NET Add-In. Enhances debugging in ways never thought possible.
JonStelly
JonStelly
I''m as big a .NET / C# fanboy as you''ll find, but I''m not sure I''d waste the time shoe-horning DirectX 8.x into a .NET app. Wait for DX9, it''s .NET enabled.
CpMan
CpMan
OK, I''ll wait.

Reality is Relative -Me and Probably somebody else
VSEDebug Visual Studio.NET Add-In. Enhances debugging in ways never thought possible.

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.

Sign in to reply to this topic.