years. I've
been trying to make the transition to ASP.NET (for what
reason, I'm not
really sure... just curiosity) I think I've finally given up
on ASP.NET,
and I'm sticking with ASP. I can't come up with any
compelling reason that
I would want to use ASP.NET. Any benefits are more than
offset by the
complexity.
I'm doing a simple welcome screen... ''Welcome Bob'', once I
log in. The
''Bob'' is coming from a single record in the ''Users'' table
that's filtered on
a session variable called ''svUserID''. With ASP, its easy and
only takes
minutes to accomplish. With ASP.NET, I've been struggling
with it for a
week.
I've concluded that if I ever have to do something other than
ASP, I will
go with Linux / PHP before going to ASP.NET.
Am I missing something?
Thanks,
Bob
ASP verses ASP.NET
%26gt; I've been working with ASP (active server pages) for
many years. I've
%26gt; been trying to make the transition to ASP.NET (for what
reason, I'm not
%26gt; really sure... just curiosity) I think I've finally
given up on
%26gt; ASP.NET, and I'm sticking with ASP. I can't come up with
any compelling
%26gt; reason that I would want to use ASP.NET.
The main one is that MS no longer officially supports ASP.
%26gt; Any benefits are more than offset by the complexity.
I'd say that's true for a lot of small to medium websites.
ASP.net is a true OOP language and is really designed for
enterprise scale
software.
%26gt; I've concluded that if I ever have to do something other
than ASP, I will
%26gt; go with Linux / PHP before going to ASP.NET.
%26gt;
%26gt; Am I missing something?
You have to want to embrace the OOP model. If not, I
agree...PHP is the way
to go.
Also, you won't get very far with ASP.net using DW. Visual
Studio is the
tool of choice for ASP.net work.
-Darrel
ASP verses ASP.NET
Hi Darrel,
I've spent much time with VS the last couple of weeks,
installing SQL Server
5 and everything it required on my local machine as well as
my server to do
their photo album example. I could get it do a few cute
database tricks
like populating a drop-down list, but again, it could not do
a simple
''Welcome Bob'' example. To me, it is definitely not worth the
intrusiveness
and complexity for anything that I do. I finally got all of
that crap
uninstalled, but I had to purchase ''Advanced Registry
Optimizer'' to fix the
damage that it caused to my registry.
I was about to say that .NET would be appropriate for a large
enterprise
application like www.Salesforce.com but I just logged into it
and they use a
.JSP extension, which I think is Linux? Salesforce.com is one
of the best
enterprise-wide database applications that I've ever worked
with.
The poster-child of the worst database enterprise application
ever is SAP.
It runs on everything Microsoft. If SAP is the pentacle of
this OOP
approach to things, then I don't want to ever go down that
path. However,
SAP consultants get a lot of money. I head a SAP consultant
say that SAP
stands for ''Shut up And Pay''.
Anyway... I did buy a DLL component that only works with
.NET, which was
the driving force behind my curiosity. I found an elegant way
to pass
session variables between the ASP and the NET world that
works great. I
think I will stick with this approach.
Bob
''darrel'' %26lt;notreal@nowhere.com%26gt; wrote in message
news:f1vhbr$mb1$1@forums.macromedia.com...
%26gt;%26gt; I've been working with ASP (active server pages) for
many years. I've
%26gt;%26gt; been trying to make the transition to ASP.NET (for
what reason, I'm not
%26gt;%26gt; really sure... just curiosity) I think I've finally
given up on
%26gt;%26gt; ASP.NET, and I'm sticking with ASP. I can't come up
with any compelling
%26gt;%26gt; reason that I would want to use ASP.NET.
%26gt;
%26gt; The main one is that MS no longer officially supports
ASP.
%26gt;
%26gt;%26gt; Any benefits are more than offset by the complexity.
%26gt;
%26gt; I'd say that's true for a lot of small to medium
websites.
%26gt;
%26gt; ASP.net is a true OOP language and is really designed
for enterprise scale
%26gt; software.
%26gt;
%26gt;%26gt; I've concluded that if I ever have to do something
other than ASP, I
%26gt;%26gt; will go with Linux / PHP before going to ASP.NET.
%26gt;%26gt;
%26gt;%26gt; Am I missing something?
%26gt;
%26gt; You have to want to embrace the OOP model. If not, I
agree...PHP is the
%26gt; way to go.
%26gt;
%26gt; Also, you won't get very far with ASP.net using DW.
Visual Studio is the
%26gt; tool of choice for ASP.net work.
%26gt;
%26gt; -Darrel
%26gt;
%26gt; I've spent much time with VS the last couple of weeks,
installing SQL
%26gt; Server 5 and everything it required on my local machine
as well as my
%26gt; server to do their photo album example. I could get it
do a few cute
%26gt; database tricks like populating a drop-down list, but
again, it could not
%26gt; do a simple ''Welcome Bob'' example. To me, it is
definitely not worth the
%26gt; intrusiveness and complexity for anything that I do.
The only complex part is the OOP mentality. Otherwise, it's a
very robust
language with a lot of great built in classes and libraries.
%26gt; I was about to say that .NET would be appropriate for a
large enterprise
%26gt; application like www.Salesforce.com but I just logged
into it and they use
%26gt; a .JSP extension, which I think is Linux?
JSP is Java (J2EE). JSP and ASP.net are 'competitors' in the
regard that
they both tend to be used for business enterprise level
application
development.
The explanation I like:
J2EE = one language, run on any server
.net = multiple languages, run on Windows Server
%26gt; Salesforce.com is one of the best enterprise-wide
database applications
%26gt; that I've ever worked with.
Right, but that's less of a judgement of the particular
framework codebase
than it is a judgement of the capabilities of the design and
development
team.
In otherwords, you can't really judge the quality (or lack
thereof) of a
particular programming language based on a couple of sample
applications.
-Darrel
''darrel'' %26lt;notreal@nowhere.com%26gt; wrote in message
news:f1vmrb$t60$1@forums.macromedia.com...
%26gt; The explanation I like:
%26gt;
%26gt; J2EE = one language, run on any server
%26gt; .net = multiple languages, run on Windows Server
%26gt;
Then there's the ''other'' J2EE - Java 2 Evil Edition.
One language.
Runs on the remnants of your ravaged sanity.
http://worsethanfailure.com/Articles/Classics-Week-The-Call-of-Codethulhu.aspx
No comments:
Post a Comment