ASP to .Net migration project

[Jean-Marc Pugin]

Hi,

Do you consider CSHARP as THE language to be used for an ASP to .Net
migration project.

ASP .Net seems a "natural" choice but as .Net is "language neutral"
and CSHARP is positioned as THE native language
we are requesting some help/advice.

Many Thanks.

[Juan T. Llibre [MVP]]

Adapted from:
http://msdn.microsoft.com/msdnmag/is...px?side=true#a

---000---
One of the most common myths is that C# code is faster
than Visual Basic code and that, therefore, C# is "the"
preferred language choice for .Net/ASP.NET.

There is a grain of truth in this, as it is possible to take
several performance-hindering actions in Visual Basic
that are not possible to accomplish in C#, such as not
explicitly declaring types.

But if good programming practices are followed,
there is no reason why Visual Basic and C# code
cannot execute with nearly identical performance.

Similar code produces similar results.

---000---

There's other considerations, too.

Migrating from VB/VBScript to VB.NET is tons easier
than migrating from VB/VBScript to C#, if your
programmers need to get up to speed with C#.

Because of that, migrating to C# is bound to be
costlier, also, ( Extended deadlines, "beginner"
coding mistakes, more bugs, etc. )

In sum, if your C# programmers are familiar with
VB/VBS, the migration to C# might be about as
easy as migrating from VB/VBS to VB.NET.

But your decision should be based on something else
than a perceived "positionin g" of C# as "the" native
language for .Net.

There's *no* preferential native language for .Net.


Juan T. Llibre
===========

"Jean-Marc Pugin" <jm*****@mobile workers.com> wrote in message
news:Oz******** ******@TK2MSFTN GP11.phx.gbl...

Hi,

Do you consider CSHARP as THE language to be used for an ASP to .Net
migration project.

ASP .Net seems a "natural" choice but as .Net is "language neutral"
and CSHARP is positioned as THE native language
we are requesting some help/advice.

Many Thanks.

[Karl Seguin]

You are asking a question that's likely to start a holy war. None of the
..Net languages are being positioned as THE native .net choice. You should
use whichever language is most familiar to yourself and your team. If you
have a strong C/C++/Java/Smalltalk background, C# will be much more natural.
If you have a VB/VBscript (ie, ASP) background, the VB.Net will obviously be
more comfortable.

I used to be of the opinion that people who want to learn .Net should do so
on C#, because, VB.Net lets you write a lot of really ugly stuff (on error
resume next, late binding, Microsoft.Visua lBasic). But what I've come to
realize is that you can write code just as bad in C#...it isn't the
language, it's the people using it. The reality is that both languages are
capable and equal tools, the only thing that changes is the person using
them.

In .Net 2.0 things are starting to change a bit. There's a divergence
between what C# and VB.Net are going to do...but if you are just starting, I
wouldn't worry about these highly technical differences (that you won't see
for another year), anyways..

Karl

--
MY ASP.Net tutorials
http://www.openmymind.net/
"Jean-Marc Pugin" <jm*****@mobile workers.com> wrote in message
news:Oz******** ******@TK2MSFTN GP11.phx.gbl...

Hi,
Do you consider CSHARP as THE language to be used for an ASP to .Net
migration project.
ASP .Net seems a "natural" choice but as .Net is "language neutral"
and CSHARP is positioned as THE native language
we are requesting some help/advice.
Many Thanks.

[John Saunders]

"Juan T. Llibre [MVP]" <no***********@ nowhere.com> wrote in message
news:et******** ******@TK2MSFTN GP12.phx.gbl...

Adapted from:
http://msdn.microsoft.com/msdnmag/is...px?side=true#a

---000---
One of the most common myths is that C# code is faster
than Visual Basic code and that, therefore, C# is "the"
preferred language choice for .Net/ASP.NET.

There is a grain of truth in this, as it is possible to take
several performance-hindering actions in Visual Basic
that are not possible to accomplish in C#, such as not
explicitly declaring types.

But if good programming practices are followed,
there is no reason why Visual Basic and C# code
cannot execute with nearly identical performance.

Similar code produces similar results.

---000---

In particular, despite the pain, I recommend turning Options Strict On
during your migration, at least once you get the project to build without
it. It will catch a lot of "performanc e-hindering actions", including some
outright bugs.

John Saunders