RE: ASP.NET 2.0 ready yet?



test

-----Original Message-----
From: Naveen@xxxxxxxxxxxxxxxxxxxxxxxxx
Posted At: Wednesday, July 27, 2005 4:14 PM
Posted To: microsoft.public.dotnet.distributed_apps
Conversation: ASP.NET 2.0 ready yet?
Subject: RE: ASP.NET 2.0 ready yet?



Hi Nick,

well, If I might have been in your place I might have prefered to work on
Beta and later while goign for production would have done with final version.

While working on betas you not only leverage new features from product but
also learn things. In the course you may even find that you are giving more
suggestions to Microsoft on how to improve a particular feature list by
submitting a bug.

Bottomline....as VS2005 are into its beta 2...I would say product is quite
stable and you can go-ahead...same is case with SQL 2005.

If you have any specific questions, fire a mail and I wouuld be more than
happy to help you out.

HTH

With Best Regards
Naveen K S


"nickpup" wrote:

> 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
>

.



Relevant Pages

  • Re: Package Microsoft.VisualStudio.Xaml has failed to load prope
    ... Is the problem occuring when you've also have SQL Server 2008 beta ... You can send feedback directly to my manager at: ... Microsoft Visual Web Developer 2008 91851-136-1692541-60726 ...
    (microsoft.public.vsnet.setup)
  • Re: ASP.NET 2.0 ready yet?
    ... The gripe I am having currently (Beta 2) is with the databound controls, ... We also planned on using SQL Server Reporting Services ... > are planned for release in Novemeber. ...
    (microsoft.public.dotnet.distributed_apps)
  • RE: ASP.NET 2.0 ready yet?
    ... Beta and later while goign for production would have done with final version. ... We also planned on using SQL Server Reporting Services from ... > features in these new releases that could help make our development more ... > are planned for release in Novemeber. ...
    (microsoft.public.dotnet.distributed_apps)
  • Re: Yukon: Password Validation Failed
    ... First of all, Yukon is in Beta 1 version, so you can experiece many errors ... In SQL Server Yukon Beta, he was unable to create SQL ... and it turns out that if setting "Password Must Meet Complexity Requirments" ...
    (microsoft.public.sqlserver.security)
  • Re: ASP.NET 2.0 ready yet?
    ... From: Ziga Jakhel ... The gripe I am having currently (Beta 2) is with the databound controls, ... We also planned on using SQL Server Reporting Services ... > are planned for release in Novemeber. ...
    (microsoft.public.dotnet.distributed_apps)

Quantcast