New app in classic ASP using .Net classes: is it daft?

[eric_mamet_test]

Hi there,

I am currently working in ASP.Net/VB.Net but I am about to embark into
a new project (part time) with a chap who's only programming experience
is classic ASP (and SQL Server).

We are thinking of him writing the front-end in classic ASP, using .Net
classes (that I'll write) exposed through Interop.

Question 1:

What sort of problems can I expect? Many?
For instance, is there any issue with upgrading a (.Net) DLL while it's
being used by a classic ASP web site through Interop (I used to use MTS
to solve this in VB6).
Are there big constraints/limitations in passing parameters back and
forth?



Question 2:
is it stupid ?



Many Thanks


Eric )

 

[Scott M.]

My advice is that for a new application this is not the way to go.

You will run into performance issues to say the least.

 

[Carlos J. Quintero [.NET MVP]]

Yes, you can find all sort of problems. For example, you have to design your
..NET classes carefully to be called from COM, not to mention performance
problems.

It is recommended to upgrade the programming abilities of your chap to
ASP.NET. I have the same argument with a friend of mine ;-)

There is a MS CD-ROM with resources to make the transition fast and surely
he will love ASP.NET compared to ASP...

--

Carlos J. Quintero

MZ-Tools 4.0: Productivity add-ins for Visual Studio .NET
You can code, design and document much faster.
http://www.mztools.com