Greetings,

Question targeted at:
================
Anyone who did network programming on early win32 platforms using
conventional MS tools such as

1. (C++ using VC++ with IDE, SDK, DDK)
2. (C language using Win32 API without using  C++ abstractions layers
such as WinSock 1.0/2.0, LanManager API directly)
3. Other equivalents ......

or MVPs, MCSDs who understand both old and new technologies who want
to pitch in, please respond. I prefer and appreciate replies in a very
conceptual level. However if you give detailed responses, artciles or
URLs I will save them and read later, but feel free to respond.

background
=========

Most of my past work until 2005 was using item 2 above. I have
attempted to port or wrap old win32 components using some kind of
socket functionality using COM to DOT NET 2003 platform and had to
quit to go programming on Unix/Linux due to necessity.

question
=======
Please give specific URLs to help me understand managed code/unmanaged
code concepts, DOT concepts without having to read heavy books. I
prefer articles and write-ups that summarizes concepts, best
practices, standards and tools to quickly move ahead.

1. How to port my old style components to platforms starting from DOT
NET 2003 and later versions?
2. Another challenge I have to deal with is being a 70% server side
programmer and 30% UI programmer, I still have to learn to manage GUI
development in the new DOT NET versions. How to go about this?
3. Finally if I were wrting new network applications, the old paradigm
does it still hold? Or should I switch to C# socket programming? If I
were to still use the old paradigm, how will I do that on DOT NET
platforms, can I get away with that?
4. At last how far have we come along with SNMP, what is Miccrosoft's
available or proposed model, MIBs if any etc.

If I asked the question to folks who write regualr apps, the answer
will come out different. But I want replies from people who navigate
the domain I am dealing with (or) MVP like gurus.

Please repond to this thread.

Help is deeply appreciated.

TIA.

b6149cee-e7b7-49c9-ad02-6da5b3e53***@t16g2000yqi.googlegroups.com...
You can do everything with C/Win32 api and sockets with VS.NET.
I don't see the problem
(and 'mvp' has nothing to do with "gurus" or any skills (!!!!) : if you post
10 crappy messages a day, you will be 'mvp' (I know what I mean...)
'mvp' program is just ridiculus...

Show quote Hide quote You mean I can open .NET 2003 or .NET 2008 and go about writing and
compiling the old style code??  Could you please show me the URLs or
details of what settings I must use to acheieve this effect in the
IDE??

TIA

Visual Studio 2003, 2005, 2008 all contain C/ C++ compilers that will any
correctly written Win32 code (C API) for both 32 & 64 bit versions of any
recent OS.

If you want to move to .NET development (C#, VB.NET etc.), you can use these
tools too.  the .NET framework is an abstraction layer on top of Win32 and
so can do nothing that Win32 can't.  What .NET _does_ do is to make it
easier to _write_ code.  So if you are writing new code, .NET is a good
choice, but there is no need to port existing working code to .NET for fear
that the APIs it uses will be obsoleted by Microsoft.

Show quoteHide quoteYou mean I can open .NET 2003 or .NET 2008 and go about writing and
compiling the old style code??  Could you please show me the URLs or
details of what settings I must use to acheieve this effect in the
IDE??

TIA

Cannot join to domain after sysprep (XP SP2)
server info on desktop
IP address in conflict..?
NETSH command doesnt work???
Windows 95
Mise en réseau
Creating VPN for domain users
No DHCP Offers on Wire
Cannot access Network Connections anymore
policies