Smart Device Extensions really isn't the issue in terms of the langauge, as
above.
Some thoughts:
VB.NET is not case sensitive but C# is; and being case sensitive resolves a
lot of potential confusions and allows clearer naming conventions if case
sensiteve. The use of delegates and event handlers is a much more
understandable implementation in C#, less typing in C# none of the End Ifs
etc. Has some nice enhancements that are not in VB.NET like lock in
threading and the commenting features are better. There is a big jump in
terms of the capability of the language from VB6 to VB.NET and it was a bit
of a shock to the VB community, to quote a VB user group. There was also, i
thing a lot of pressure when designing the language from die hard VBers to
keep certain things in or not to change features. I think this compromised
it a bit eg. "Dim". Isn't this a hang over from QBASIC!
The Macro generator in VS.NET generates its code in VB.NET not C#, which is
a minor point. I used VB though all it's incarnations to the max, hated
VBScript, and love C# now.
It's a mute point at MS, each unto there own.
Ben
[quoted text, click to view] "pragya" <prags_l@rediffmail.com> wrote in message
news:2af501c33f50$e2f163f0$a401280a@phx.gbl...
> Hi All,
> I m a developer switching to Dot net. We write
> applications for handheld devices. In dot net we write
> application using Smart Device Extensions. Now my question
> is this that we should choose VB.net or C# as a platform
> IDE. Please provide all the plus minus based on handheld
> device development.I shall be highly obliged , if u please
> send me a mail regarding this.
>
> Thanks & rgds
> Pragya