>
I'm not much of a VB person but just by looking at few pieces of code from an application it seems that your only entry point would a form to an MDI Application.
>

Again, you can create a Sub Main to act as your entry point. You have neglected to include this in your response..

This is a weak defense on your part.


>Here's a quote from http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cscon/html/vcoricstartpage.asp:
>
>"Microsoft C# (pronounced C sharp) is a new programming language designed for building a wide range of enterprise applications that run on the .NET Framework. An evolution of Microsoft C and Microsoft C++, C# is simple, modern, type safe, and object oriented. C# code is compiled as managed code, which means it benefits from the services of the common language runtime. These services include language interoperability, garbage collection, enhanced security, and improved versioning support."
>
>Languages like C and C++ have always been ahead of the game when it comes to enterprise development. I don't need to program in VB to know it's weakness I've worked side-by-side with VB guys and I know the limitations of VB. Until now VB couldn't make full use of MTS and COM+ which by the way (in case you weren't aware) is widely used in the enterprise world.
>

>On the other hand, C and C++ have been right there in the front line handling all the heavy loads that VB couldn't handle and to add pain to the insult I've used VFP in place where VB just fell apart - that's how poor of a language it is (that's a fact). And so there it is, coming straight from Microsoft C# is part of the C evolution. People are moving to this language because of that reason - not because it has a "C" in the title (contridicting your statement from other threads).
>

I guess it begs the question of why you have not programmed in C++ heretofore..

Quoting the docs as a method of proving the matter it asserts is nothing more than hearsay. Some objective evidence, other than quoted snippets would be far more valuable in proving what you say.


>You forget .NET has only been around for just under 2 years, which most has been under beta. We're all on the same plain when it comes to .NET - but just to satisfy your couriousity I'm preparing lesson plans to teach a class in .NET with an emphasys on Business Objects and COM+. You're more than welcome to attend so that you can learn about the power of C#.
>

I forget??? I don't think so...

Given what you are saying here, I have two comments about your "lesson plans"

1. The chances are good that you are simply regurgitating material - adding
very little in the way of your own insights.

2. Given that you have invited me to attend, I would have to take a pass. You
have annointed yourself to expert status that quite frankly, I don't think
you have earned. To put it gently, I think you over-estimate your abilities
here. Given the choice, I think I could teach myself a lot more than you
could hope to learn yourself...< s >.. Comparing our resumes, it would be
as if I went to a high school senior to give me a civics lesson on the
Constitution. Thanks anyway - but you presume too much here...

><<
>Right, I forgot these guys write books for the money <g>.
>
>Have you actually evaluated the technical merits of most books? Or, do you blindly believe everything you read??????
>
>Bascially, you are spouting (regurgitating) FACTS without any real/substantive understanding of what you are talking about.
>>>

Right... I have written 5 books...Over 50 feature articles - and quite frankly, probably one of the most cited VFP resources on MSDN...< s >

Right, I have no idea what I am talking about here... Get a clue Victor...

>
I think it's obvious that I don't "blindly believe everything" I read - otherwise I'd be in the posse of groupies you have blindly chasing you.
<

Ouch, that hurt... You are getting a bit personal here...

<<
Everything I posted has been published more than a dozen times and backed by Microsoft as well as "regurgitated" (as you put it) by others in this forum.
<<

Cite the 12 places you have been published. How many MSDN articles have you written. Other than the UT, where have you been published?