C# vs. ASP.NET for web services?

[Guest]

I want to use .NET for writing web services that will mainly call SQL Server
(2000) stored procedures in a database. What are the
advantages/disadvantages of using C# vs. ASP and vice versa?

Also, if any one is familiar with ColdFusion MX, what are the
advantages/disadvantages of using .NET (one of the two languages above) to
write the same web service vs. using CFMX?

Thanks,
Brett

 

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,


ASP was not intended to be used with web services and lack the support
found natively in the .net environment. So there is not much point going
with ASP at this time.

Creating a web service in VS.NET is super easy, just select the correct
project type and all the needed code is ready to use.

If the main purpose of the web service is access SQL server, you should
know that SQL server provide a similar functionality with an extension inSQL
2K and natively in 2005 IIRC , take a look at this link:
http://msdn.microsoft.com/SQL/sqlreldata/XML/default.aspx

regarding coldfusion MX I have no experience with it, the view I have of
it ( may be incorrect ) is that is just a scripting language in the same way
of ASP , and do not provide the OOP of .NET


so I would stick with .NET

Cheers,

 

[Nergal]

Hi Brett,

If you use asp.net you *can* use c# for all the code. Having used classic
asp for years I can tell you that asp.net is great. Once you get used to it
its an easy model for writing webpages and the tools and community support
are great.

Don't know about ColdFusion so I can't compare but the possibilites of
asp.net are nearly endless.