Re: MFC under VS2010
I just worked on another complete .NET application and since it was very
file system intensive I had to resort to pInvoking all sorts of Win32
functions since the .NET System.IO implementation can't support file paths
longer than 260 chars. Sure, Windows supports it, Win32 supports it, but I
guess the .NET architects thought they didn't need to. So far I haven't
been able to do any C# programming without calling on Win32 functions
directly.
I don't find the GUI editor to be that much better either. I do like how
some things, like font settings, are settable in the properties, but other
than some conveniences like that, I don't see the big deal.
Tom
"Ajay Kalra" <ajaykalra@yahoo.com> wrote in message
news:644c9093-eec0-4e02-bc0d-01202e021824@x12g2000yqx.googlegroups.com...
On Mar 29, 7:24 pm, "David Ching" <d...@remove-this.dcsoft.com> wrote:
"Ajay Kalra" <ajayka...@yahoo.com> wrote in message
The point is, if native development is the only trick in your bag, you
are
not going to be well positioned to develop Windows in the future. MS is
slowly making essential capabilities managed-only.
I have forgotten what native development is. It seems odd but I hope I
dont ever have to do that for GUI development. For server side work,
unmanaged is OK.
--
Ajay
-- David