Use ASP.NET 1.1 or 2.0?

[Pieter]

Hi,

For my development I use VB.NET and C#. In the company w're using 2003 and
2005.
Now we want to make an intranet-application in ASP.NET, but neither me
neither the developer have a lot of experience with ASP.NET.

But one of the things I do have a lot of experience with is Visual Studio
2005.NET: When using it for Winforms Applications it is terrible and buggy.
This made me make the decision to limit the development in 2005, and use
most of the time 2003.

My questions are:
- I'm sure that ASP.NET must have a lot of new/cool/helpfull/nice featurs
compared with 1.1. But are they worth using Visual Studio 2005?
- Is Visual Studio 2005 also that buggy when developing in ASP.NET 1.1?
- What are the new features in ASP.NET 2.0 that are really helpfull, speed
up the development, ease the task etc...

So in other words: What do you advise? The main tasks of the
intranet-application is jsut consulting and adding data in sql server
databases.

Any help, hints or links would be really appreciated!

Thanks a lot in advance,

Pieter

 

[Karl Seguin [MVP]]

Different people have had different experience with 2005. For me it's been a
growing pain, but I'm mostly behind my problems and have adjusted my
programming to fit wiht the IDE quirks (not ideal, but it works!). There's
still some difficulty around the new project model, but a beta of the 2003
project model for 2005 is available.

you can't use vs.net 2005 to develop 1.1.

I think generics is still the most useful new feature in 2005. ASP.NET has
had a lot of goodness added to it, but I find a lot of it to be eye candy -
good for demonstrations, useless in serious applications. That said, there
are some really nice features like native support for master pages, greater
programmatic control for output caching and better declarivitive programming
environment.

I'd go with 2005 for the learning experience.

Karl

 

[S. Justin Gengo [MCP]]

Pieter,

I've also switched to 2.0 and have found the learning experience to be a
great one. I haven't run into too many bugs yet. And I have to say I really
like the added features. Just using master pages is wonderful. Also the new
default settings are much nicer (automatically going to the source view of a
page instead of the display view and having the page set to flow layout just
to name a couple). They are very small things but they make development much
more enjoyable. Plus this is the way MS is going so if you're going to use
..NET you may as well learn the latest version rather than be behind by
learning something that will slowly fade.

--
Sincerely,

S. Justin Gengo, MCP
Web Developer / Programmer

www.aboutfortunate.com

"Out of chaos comes order."
Nietzsche

 

[Daniel Fisher\(lennybacon\)]

So said 2.0 contains everything I wanted to be in there since 1.0



--Daniel
http://staff.newtelligence.com/danielf/




-----Original Message-----
From: Pieter [mailto[email protected]]
Posted At: Tuesday, January 24, 2006 11:13 AM
Posted To: microsoft.public.dotnet.framework.aspnet
Conversation: Use ASP.NET 1.1 or 2.0?
Subject: Use ASP.NET 1.1 or 2.0?

Hi,

For my development I use VB.NET and C#. In the company w're using 2003
and
2005.
Now we want to make an intranet-application in ASP.NET, but neither me
neither the developer have a lot of experience with ASP.NET.

But one of the things I do have a lot of experience with is Visual
Studio
2005.NET: When using it for Winforms Applications it is terrible and
buggy.
This made me make the decision to limit the development in 2005, and use

most of the time 2003.

My questions are:
- I'm sure that ASP.NET must have a lot of new/cool/helpfull/nice
featurs
compared with 1.1. But are they worth using Visual Studio 2005?
- Is Visual Studio 2005 also that buggy when developing in ASP.NET 1.1?
- What are the new features in ASP.NET 2.0 that are really helpfull,
speed
up the development, ease the task etc...

So in other words: What do you advise? The main tasks of the
intranet-application is jsut consulting and adding data in sql server
databases.

Any help, hints or links would be really appreciated!

Thanks a lot in advance,

Pieter

 

[Pieter]

Ok thanks guys!
It seems that ASP.NET 2.0 isn't that buggy as Winforms

 

[Jeff]

Don't be so quick! I just asked more or less the same question recently and
got the opposite response from users of both; specifically that WinForms is
mostly stable while ASP.NET is unstable in 2.0.

Personally I'm going to sit this one out and wait for 2.x. Apparently there
is a service pack due sometime near mid-2006. Can't wait! Looking forward to
all the new features in .NET 2005/sp1 and Framework 2.x.

-FWIW

 

[Rob R. Ainscough]

VS 2003 is the worst pile of crap I've seen in a long time from Microslop
and I can see why Microslop are loosing developers by the droves to other
technologies.

VS 2005 has got issues also (be prepared to have a very powerful development
PC) but they pale in comparison to the issues VS 2003 had -- at least on the
Windows Forms application side. The VS 2005 IDE has many much needed
improvements that make it a must have for me and I'll have to suffer thru
the rest.

VS 2005 ASP.NET 2.0 still leaves MUCH to desired and I'm not sure if it is a
step forward or backward from ASP.NET 1.1 in VS 2003. It looks and feels
like the VS 2005 Windows Forms side progressed well, but the ASP 2.0 side
just fell flat.

I will however NEVER migrate again, if Micrslop can't even migrate their own
web apps from ASP.NET 1.1 to ASP.NET 2.0 without a ton of issues, then it
doesn't look good. As far as I'm concerned this is the end of the
technology line I'm willing to go with Microslop unless they come up with a
100% compatible migration path on ALL fronts. I'm done with the migration
issues and so are my clients, they WILL NOT pay for another round.

Rob.

 

[Brooke]

Ok, what are the alternatives??? I am very interested as I am just starting
ASP.NET and I have both VS 2003 & VS 2005. I would like to chose the right
path before I get to far along.

Thanks.

 

[john smith]

Don't be so quick! I just asked more or less the same question recently and
got the opposite response from users of both; specifically that WinForms is
mostly stable while ASP.NET is unstable in 2.0.

Personally I'm going to sit this one out and wait for 2.x. Apparently there
is a service pack due sometime near mid-2006. Can't wait! Looking forward to
all the new features in .NET 2005/sp1 and Framework 2.x.

-FWIW

It's really a matter of preferences, opinions and personal experiences.
I haven't played much with winforms yet in 2005, but from the ASP.NET
point of view, it is VERY stable (any of us at work yet have to have a
single problem). No real problems with the IDE either (a couple
intellisense crashes, that's about it really; well, a bit slower, but so
many enhancements too). And the advances are absolutely wonderful...
From nullable types and generics to master pages and membership/role
providers. It's sooooo much better - I don't EVER want to go back to
1.x! v2.0 is FAR better all-around!

 

[Rob R. Ainscough]

The right path, unfortunately there is still no single "Right" path -- if
you want to do anything creative you'll need to know JavaScript with ASP.NET
and HTML, and XHTML, and XML, and CSS, and then the language of choice C#,
VB, and then you have to buy into ADO.NET way of getting data -- this is
just on the Microsoft side. Will you have time to explore all the possible
options to make the absolutely best decision -- no, not unless you teach or
something where you don't have constant flow of new projects and new revenue
to generate.

Is there anything more simple -- no, it is just getting worse and worse with
more and more unless options for doing the same thing.

If I were to look into the future, I'd look at things like ClickOnce, AJAX,
and anything else that can remove 99% of itself from the client browser.
Unfortunately the current state of affairs for web development is that too
many developers and tinkers got it "their" way.

 

[john smith]

Ok, what are the alternatives??? I am very interested as I am just starting
ASP.NET and I have both VS 2003 & VS 2005. I would like to chose the right
path before I get to far along.

Alternatives to ASP.NET? Too many! Tons of languages and associated
frameworks - more than you'd ever have time to look at or learn.

-Mono (Linux port of ASP.NET)
-Classic ASP (vbscript or jscript)
-Java (J2EE, JSP, etc) with tons wildly varying frameworks (including
some mature and advanced but very complex ones), running on a variery of
JVMs...
-PHP; tons of frameworks again; often/usually used along with MySQL
-Ruby; Rails being the most-known framework (but not the only one)
-Python, various frameworks again (cherrypy, zope, etc)
-Perl, ... (CPAN, etc)
-C (CGI)

And a bunch of other languages... (tcl, lua, etc), other things like
ColdFusion and such...

You have to consider all kinds of things:
-The platforms they run onto (windows? *nix? etc)
-The application servers they run onto (IIS? WebSphere? etc)
-The language you're programming into (syntax, etc)
-The main frameworks (what they offer, how hard/learning curve, etc. you
pretty much have to learn them to know in the first place... kind of a
catch 2 2)
-How good the development tools are (VS2005? Eclipse? ...)
-The advanced features it has or lacks, including interoperability (web
services namely)
-How much employment you can expect to find for each (and how much it pays)
-*OVERALL* costs (cost of platform/OS, cost of dev tools, cost of app
server/databases commonly used, web hosting costs, training costs, etc).

ETC!!! There is so much more to it, so as you can see it's not exactly
an easy choice. And it very much depends on your needs and preferences...

You'll also need to know some database technologies (which again vary by
whatever you chose previously - ADO.NET or JDBC or whatever); that
also means knowing the databases in particular you'll be using (SQL
Server/DB2/Oracle/Jet/MySQL/PostgreSQL/etc) - at least basic admin but
preferably the "sproc dialect" it uses and all. That's another fun
choice - just like the previous one. Also add XML to this list...

Nevermind you will still need to know about a lot of other stuff
regardless (xhtml, css, javascript and such basic web things), a lot of
programming stuff (from regular expressions, patterns, SQL, good
commenting, XML, proper documentation, UML, using source control
management apps, etc), tons of related apps (bug trackers, help
authoring, making installers, unit testing, etc). So even once you've
made the previous 2 choices, you're not quite done...

My personal choice is ASP.NET 2.0:
-wicked, powerful (.NET) framework (v2.0), one of the best IMHO
-great languages (C# for me; one of the very best languages ever made)
-great development tools: VS2005 and loads of amazing 3rd party tools
like Visual Assist X, dotTrace Profiler, CodeRush & Refactor!, VS.Net
Code Print, PromptSQL, CodeSmith, so many to list... tons of great free
stuff like NDoc too; Visio is quite handy as well.
-great documentation (msdn, newsgroups, sites like codeproject, great
developer blogs, MSDN Mag, PDC, *TONS* of stuff!!!)
-great support
-very good interoperability (perhaps the platform with the best support
for web services and WCF will only improve on this)
-so much of the boring repetitive stuff I absolutely hate are now
unnecessary (thanks to things like forms authentication & various
providers); ~70% less code to write - and they actually deliver on these
claims; I truly enjoy coding this way!
-great performance, powerful caching built-in, easy deployment
-reasonable costs (win2003 vs linux w/ support; IIS vs webshpere; sql
server vs oracle/db2...)
-lots of new, exciting, powerful technologies coming soon (WPF, WCF, WFF)

Tons more things, but I guess that's a good start anyways