Re: VC .Net not mature?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: David McClarnon (dmcclarnon_at_ntlworld.com)
Date: 10/20/04 

Date: Wed, 20 Oct 2004 23:38:50 GMT

The unProfessional wrote:

> To the VC .Net'ers out there...
>
> I noticed alot of strange behavior in the way VC .Net apps behave in the
> IDE. It's a bit odd, so maybe people have workarounds. I'm worried to
> devote my project to the managed/unmanaged heuristic because these early
> issues make me feel VC .net just isn't mainstream (or complete) enough yet
> to depend on.
>
> Anyway, one of the things is the code formatting. When adding event
> handlers and such, the code is formatted like so...
>
> public void Func (...)
> {
>
> }
>
> with the brackets strangely indented. Also, the functions are often jammed
> right up against another, and even sometimes, the bracket scope gets messed
> up.
>
> public void Func1 (...)
> {
>
> public void Func2 (...)
> {
>
> }
> }
>
> .. automatically, by the IDE... = BAD!
>
> This is contrary to the way IDE-generated code behaves in purely managed
> apps (C# or VB.net), hence my confusion about the stability of VC .net.
>
> Also... why do event handlers automatically get dumped in the .h file?
> Seems strange... C++ projects almost always, at least if style is an issue,
> separate implementation from declaration (Cpp files), both for organization
> and compilation issues. However, VC .Net seems to ignore this convention
> and throw everything into the header files. Kind of annoying ;)
>
>
> Anyway, I guess the real question is, is VC .Net a good idea for a large
> project? Is it fairly straightforward to combine alot of previously written
> unmanaged code with managed interfaces and windows forms?
>
> Thanks for any and all input!!
>
> - Bill
>

I generally only reserve C++.NET for when I need to use it. Then I write
an assembly to wrap up whatever native code I want to access, and write
the vast majority of the code in C# instead.

Why ?

I find C++.NET a pain to write in to be honest. And with the .NET
architecture it's so easy to link an assembly into a C# project.

C# is much better set up to use .NET than C++. For a start the namespace
  character is period not colon which means I only have to hold down one
key instead of 2 (shift to get colon).

And the intellisense is much better.

This is just my way of working which has been built up over about the
last year and a half.

David.