Win32 app. or .net App.?

[Chi Tang]

Hi,

I need to implement a stand alone gui application which need to call some
other regular DLL functions (unmanaged code). Should I use .net with C# or
just use Win32 API to write this exe? Is it easy to call any DLL function
from .net/C# program?

The 2nd question is that on a win32 app, I can use 'UNICODE' to support
localization (support different languages). How about on .net? Is it
straightforward? On win32 application, I can have multiple resource for
multiple languages. How is this done on .net? Thanks for any help,

CT

[RiteshDotNet]

In C# you can easily incorporate win32 dll by using interop it will work fine
for localization window C# application its versimple only need to do
change form localizable property true and select Langauge in that case it
will create resx file for that specific language
then in programm set system.thread.currentcultureinfo
for localization this link might be usefull for you
http://www.microsoft.com/globaldev/g...otneti18n.mspx
"Chi Tang" wrote:

Hi,

I need to implement a stand alone gui application which need to call some
other regular DLL functions (unmanaged code). Should I use .net with C# or
just use Win32 API to write this exe? Is it easy to call any DLL function
from .net/C# program?

The 2nd question is that on a win32 app, I can use 'UNICODE' to support
localization (support different languages). How about on .net? Is it
straightforward? On win32 application, I can have multiple resource for
multiple languages. How is this done on .net? Thanks for any help,

CT

[Elp]

On Fri, 7 Jan 2005 23:16:15 -0800, Chi Tang wrote:

I need to implement a stand alone gui application which need to call some
other regular DLL functions (unmanaged code). Should I use .net with C# or
just use Win32 API to write this exe? Is it easy to call any DLL function
from .net/C# program?

As RiteshDotNet said, it's quite easy to call Win32 API from C# (via
Interop) provided that the API signatures are simple enough. However, if
your application is mostly about calling Win32 API that have no equivalent
in .NET, then it may be easier to just do as a Win32 application. If
calling Win32 API is just a small part of your application, then go to C#.
You won't regret it.

[Brumarhindi Chicopella]

Chi Tang wrote:

Hi,

I need to implement a stand alone gui application which need to call some
other regular DLL functions (unmanaged code). Should I use .net with C#
or
just use Win32 API to write this exe? Is it easy to call any DLL function
from .net/C# program?

I do it all the time.

You should also see if you can get the source for the DLLs and convert those
to .Net.

COM needs to die.

--

Being born is like being kidnapped. And then sold into slavery.

a.warhol

[Fredrik Wahlgren]

"Brumarhindi Chicopella" <bc@__acraz_.deapusi> wrote in message
news:vx****************@newsread3.news.pas.earthli nk.net...

Chi Tang wrote:

Truncated

COM needs to die.

Why?

/Fredrik

[RiteshDotNet]

Look if you wanted to use simple win32 dll (Com component) then in that case
it will easy to do in C# , but if you wanted to use complex win32 API then in
that case go to any vb/vc com based application which gives better support
"Elp" wrote:

On Fri, 7 Jan 2005 23:16:15 -0800, Chi Tang wrote:

I need to implement a stand alone gui application which need to call some
other regular DLL functions (unmanaged code). Should I use .net with C# or
just use Win32 API to write this exe? Is it easy to call any DLL function
from .net/C# program?

As RiteshDotNet said, it's quite easy to call Win32 API from C# (via
Interop) provided that the API signatures are simple enough. However, if
your application is mostly about calling Win32 API that have no equivalent
in .NET, then it may be easier to just do as a Win32 application. If
calling Win32 API is just a small part of your application, then go to C#.
You won't regret it.