MBR IT/.NET 247 : Best Practices/Mixing ASP/ASP.NET on ASPFriends.com 'aspngmigrate' list

Best Practices/Mixing ASP/ASP.NET

Messages

Related Types

This message was discovered on ASPFriends.com 'aspngmigrate' list.
Responses highlighted in red are from those people who are likely to be able to contribute good, authoratitive information to this discussion. They include Microsoft employees, MVP's and others who IMHO contribute well to these kinds of discussions.

Joshua D. Little

-- Moved from [aspngfreeforall] to [aspngmigrate] by Charles M. Carroll <Click here to reveal e-mail address> --Hey all,My manager just told me that he doesn't think mixing ASP and ASP.NET is a good idea--"it just seems inherently flawed..." The only reason I need to do this is because ChartFX has not released their .NET charting controls (and said manager doesn't want me to spend time developing my own w/ System.Drawing). So, since we have the old (ASP 2/3) version of the ChartFX control (that he wants me to use), I would have to run the chart pages in ASP instead of ASP.NET. The rest of the app, however, I was planning on building (and have already built some) in .NET.I told him that I don't think there's a good reason not to mix code, but he said "what about our other developers (who may have to work on this at some point)?" The only reasons I can think of that mixing wouldn't be good would be session transferrence, which isn't a problem since I don't need sessions, and the other problem would be common functions I write for the app that would have to be written in both versions. I don't think the second is a big deal because I don't see myself writing too many for this particular app. He ultimately said he'd get a consensus from everyone and that if I care, I should convince the others that mixing is fine. I'm concerned about this because a couple of them haven't even touched .NET and are not hard-core programmers, so they're already kind of shying away from it. The others could go either way.So I need good reasons to use .NET--reasons that would outweigh potential difficulties in a mixed environment, such as the one mentioned above. I really, REALLY prefer to program in .NET because, primarily, I like the object-oriented nature and the code/HTML separation. I think it runs faster, but we don't have time for benchmarks. ;)Any thoughts?Thanks.--Ambrose

Reply to this message...

Matias Woloski

Joshua,
I imagine that ChartFX is a set of COM objects. ASP.NET gives you the power
to interop with COM. So I don't see the need of mixing asp/asp.net code.
Take a look at 'COM interop' in the docs.

Matias

[Original message clipped]

Reply to this message...

Jeff Laughlin

Unfortunately, if I were your manager at this point in time I'd need to
agree with him... a mixed codebase scares me. However, this does not
mean the issue is dead. Depending on the charting levels you need you
could spend a few hours at home and build up a "good-enough" system then
rip it out and replace once a full charting package is available. You
could also try some of the interop abilities of .net to wrap the com
objects of ChartFX (never used them so I have no clue how easy/hard this
would be).

Oh, and of course the third (and probably) best option is to simply
bribe 50% of the programmers... a nice shiny red wrox beginning asp.net
book may do the trick.

-----Original Message-----
From: Joshua D. Little [mailto:Click here to reveal e-mail address]
Sent: January 24, 2002 6:14 PM
To: aspngmigrate
Subject: [aspngmigrate] Best Practices/Mixing ASP/ASP.NET

-- Moved from [aspngfreeforall] to [aspngmigrate] by Charles M. Carroll
<Click here to reveal e-mail address> --

Hey all,

My manager just told me that he doesn't think mixing ASP and ASP.NET is
a good idea--"it just seems inherently flawed..."

The only reason I need to do this is because ChartFX has not released
their .NET charting controls (and said manager doesn't want me to spend
time developing my own w/ System.Drawing). So, since we have the old
(ASP 2/3) version of the ChartFX control (that he wants me to use), I
would have to run the chart pages in ASP instead of ASP.NET. The rest
of the app, however, I was planning on building (and have already built
some) in .NET.

I told him that I don't think there's a good reason not to mix code, but

he said "what about our other developers (who may have to work on this
at some point)?" The only reasons I can think of that mixing wouldn't
be good would be session transferrence, which isn't a problem since I
don't need sessions, and the other problem would be common functions I
write for the app that would have to be written in both versions. I
don't think the second is a big deal because I don't see myself writing
too many for this particular app.

He ultimately said he'd get a consensus from everyone and that if I
care, I should convince the others that mixing is fine. I'm concerned
about this because a couple of them haven't even touched .NET and are
not hard-core programmers, so they're already kind of shying away from
it. The others could go either way.

So I need good reasons to use .NET--reasons that would outweigh
potential difficulties in a mixed environment, such as the one mentioned

above. I really, REALLY prefer to program in .NET because, primarily, I

like the object-oriented nature and the code/HTML separation. I think
it runs faster, but we don't have time for benchmarks. ;)

Any thoughts?

Thanks.

--Ambrose

| [aspngmigrate] member Click here to reveal e-mail address = YOUR ID
| http://www.asplists.com/asplists/aspngmigrate.asp = JOIN/QUIT

Reply to this message...

Charles D. Carroll (VIP)

The tool I used to moderate is an ASP.net app (.aspx extension) that I =
use 24 x 7 and is mission critical and lightning fast.

It calls a COM component constantly. The call looks like it is calling a =
native .NET component despite the fact is a legacy COM component and has =
NEVER EVER failed and runs much faster than classic calling same COM =
components.

Calling COM and COM+ objects in .NET works BETTER than calling them in =
Classic and I can't percieve a real world speed penalty!

The entire website LearnAsp.com is 80% ASP and 20% .net -- while the =
.NET stuff is faster to write easier to maintain and perfect stability =
since release of Beta1/Beta2 some of my team has to reuse some ASP code =
and considers the ability to mix a godsend while they work on porting a =
couple scripts at a time.

http://www.aspfriends.com/aspfriends/moderatehow.asp

----- Original Message -----
From: "Jeff Laughlin" <Click here to reveal e-mail address>
To: Click here to reveal e-mail address
Sent: Thu, 24 Jan 2002 18:44:14 -0500
Subject: RE: [aspngmigrate] Best Practices/Mixing ASP/ASP.NET

Unfortunately, if I were your manager at this point in time I'd need to
agree with him... a mixed codebase scares me. However, this does not
mean the issue is dead. Depending on the charting levels you need you
could spend a few hours at home and build up a "good-enough" system then
rip it out and replace once a full charting package is available. You
could also try some of the interop abilities of .net to wrap the com
objects of ChartFX (never used them so I have no clue how easy/hard this
would be).

Oh, and of course the third (and probably) best option is to simply
bribe 50% of the programmers... a nice shiny red wrox beginning asp.net
book may do the trick.

-----Original Message-----
From: Joshua D. Little [mailto:Click here to reveal e-mail address]=20
Sent: January 24, 2002 6:14 PM
To: aspngmigrate
Subject: [aspngmigrate] Best Practices/Mixing ASP/ASP.NET

-- Moved from [aspngfreeforall] to [aspngmigrate] by Charles M. Carroll
<Click here to reveal e-mail address> --

Hey all,

My manager just told me that he doesn't think mixing ASP and ASP.NET is=20
a good idea--"it just seems inherently flawed..." =20

The only reason I need to do this is because ChartFX has not released=20
their .NET charting controls (and said manager doesn't want me to spend=20
time developing my own w/ System.Drawing). So, since we have the old=20
(ASP 2/3) version of the ChartFX control (that he wants me to use), I=20
would have to run the chart pages in ASP instead of ASP.NET. The rest=20
of the app, however, I was planning on building (and have already built=20
some) in .NET.

I told him that I don't think there's a good reason not to mix code, but

he said "what about our other developers (who may have to work on this=20
at some point)?" The only reasons I can think of that mixing wouldn't=20
be good would be session transferrence, which isn't a problem since I=20
don't need sessions, and the other problem would be common functions I=20
write for the app that would have to be written in both versions. I=20
don't think the second is a big deal because I don't see myself writing=20
too many for this particular app. =20

He ultimately said he'd get a consensus from everyone and that if I=20
care, I should convince the others that mixing is fine. I'm concerned=20
about this because a couple of them haven't even touched .NET and are=20
not hard-core programmers, so they're already kind of shying away from=20
it. The others could go either way.

So I need good reasons to use .NET--reasons that would outweigh=20
potential difficulties in a mixed environment, such as the one mentioned

above. I really, REALLY prefer to program in .NET because, primarily, I

like the object-oriented nature and the code/HTML separation. I think=20
it runs faster, but we don't have time for benchmarks. ;)

Any thoughts?

Thanks.

--Ambrose

| [aspngmigrate] member Click here to reveal e-mail address =3D YOUR ID
| http://www.asplists.com/asplists/aspngmigrate.asp =3D JOIN/QUIT

Reply to this message...

Josh Little

Thanks! I can't believe I forgot about this! It actually hit me as I
was sending the post, but I thought I'd see what you guys had to say all
the same. I appreciate the input!

--Ambrose

[Original message clipped]

Reply to this message...

Eurika Way

Hello there,

The one major advantage of ASP.net is it has achieved a perfect or near
perfect components of 'mixed fruit jam'
(HTML ,Scripting lang..etc) Given that its not
the brightest idea to complicate by using ASP and ASP.net and introduce a
new flavour. Ofcourse if you
do try - BRAVO for you are brave and creative to have thought the thought
and all the best in your endeavour.
For me, its hard to digest my jam as is.

Arshi

[Original message clipped]

_________________________________________________________________
MSN Photos is the easiest way to share and print your photos:
http://photos.msn.com/support/worldwide.aspx

Reply to this message...

MBR BootFX
Best-of-breed application framework for .NET projects, developed by Matthew Baxter-Reynolds and MBR IT

	Copyright © Matthew Baxter-Reynolds 2001-2008. '.NET 247 Software Development Services' is a trading style of MBR IT Solutions Ltd.
	Contact Us - Terms of Use - Privacy Policy - www.dotnet247.com