Most ASP is coded in VBScript. There are two possible options:

1. Leverage the familiarity with VB and move to VB.NET in your ASP.NET
2. Move into C# to avoid trying to code in ASP.NET using an ASP methodology

Having seen too many ASP.NET sites that mimic ASP sites, the second option
is more appealing to me. The question is whether the learning curve of C# is
a bit too steep for your timetable. If no, I would jump to C#. The main
benefit is your developers will see the paradigm shift as part of the
language learning process rather than attempt to duplicate results in a new
environment. In order to code .NET properly, you need to make the paradigm
shift; if not, you will simply be coding ASP in a compiled environment, which
does not take advantage of the benefits of .NET. In addition, moving to C#
removes the "training wheels" of VB.NET, forcing you to use .NET Framework
classes.

---

Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************

Cowboy has a good point about forcing change.

I don't agree that C# is any more "native" than VB .NET: they generate the same MSIL!

Expect C# to get more techhie features (virtual members); VB to get more user-friendly stuff (edit and continue).

Which you choose for a project depends almost 100% on personnel in my opinion. VB folks are happier in VB .NET, C and Java folks might be happer in C#. I don't know about the Cobol folks...

-- Jeff
 
 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.