Re: ASP.NET 2.0 ready yet?
- From: "test" <test@xxxxxxx>
- Date: Thu, 28 Jul 2005 23:29:50 -0700
-----Original Message-----
From: Unknown
Posted At: Friday, July 29, 2005 11:51 AM
Posted To: microsoft.public.dotnet.distributed_apps
Conversation: ASP.NET 2.0 ready yet?
Subject: Re: ASP.NET 2.0 ready yet?
-----Original Message-----
From: Ziga Jakhel
Posted At: Thursday, July 21, 2005 2:18 AM
Posted To: microsoft.public.dotnet.distributed_apps
Conversation: ASP.NET 2.0 ready yet?
Subject: Re: ASP.NET 2.0 ready yet?
I did it in june, and am more or less not sorry for it.
The gripe I am having currently (Beta 2) is with the databound controls,
where the automatic databinding still has a few quirks. If you stick with
the asp.net 1.1 approach with a few modifications for 2.0 compliance you
should be more or less fine. I have found nothing really major with the
framework itself, but the regular beta problems of a somewhat sluggish and
sometimes buggy IDE and an occasional bug or two.
The second gripe is the lack of documentation for anything beyond demo
basics. But this will improve in time.
In the end it really depends on what your requirements are and what you plan
to do with the application. Myself, I try to develop only on 2.0 from now
on, as the framework and tools are stable enough for these few slow months.
The guys asp.net 2.0 and the VS 2005 teams really are doing a great job.
As for the sql 2005, it should be really stable, even more then asp.net 2.0,
so say the ms guys, who claim they've been running it for almost a year now
internally.
Regards,
Ziga Jakhel
MCSD.NET
ziga.jakhel(a)rrc.si
"nickpup" <nickpup@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DF5A3800-6BE2-459D-9BC4-263179232DF8@xxxxxxxxxxxxxxxx
> We are working on the design of our new web site, which we initially
> targeted
> for ASP.NET 1.1. We also planned on using SQL Server Reporting Services
> from
> SQL Server 2000. However, I have been reading about ASP.NET 2.0, as well
> as
> vs.net 2005 and SQL Server 2005, including the fact that they are planned
> for
> release in Novemeber.
>
> My questions is - should we consider using the beta products for our
> project, with the thought that they are relatively stable and production
> versions will be out in a few months? I do see a number of attractive
> features in these new releases that could help make our development more
> efficient./effective.
>
> So are these products stable enough at this point?
>
> I know We are working on the design of our new web site, which we
> initially
> targeted for ASP.NET 1.1. We also planned on using SQL Server Reporting
> Services from SQL Server 2000. However, I have been reading about ASP.NET
> 2.0, as well as vs.net 2005 and SQL Server 2005, including the fact that
> they
> are planned for release in Novemeber.
>
> My questions is - should we consider using the beta products for our
> project, with the thought that they are relatively stable and production
> versions will be out in a few months? I do see a number of attractive
> features in these new releases that could help make our development more
> efficient./effective.
>
> I know they by definition beta, and there will probably be issues. I am
> not
> looking for any guarantes, or to hold anyone to answer, just general
> impressions. Are these products stable enough at this point?
>
> Thanks in advance,
> nickpup
>
.
- Prev by Date: Re: ASP.NET 2.0 ready yet?
- Next by Date: re: ASP.NET 2.0 ready yet?
- Previous by thread: Re: ASP.NET 2.0 ready yet?
- Next by thread: re: ASP.NET 2.0 ready yet?
- Index(es):
Relevant Pages
|
