bakscliter
New Member
I am working on a project for a small company and we had agreed upon using ASP.NET. Now their network guy has changed his mind and is concerned that it is too soon to be using ASP.NET in production. We are planning for an end of June/early July rollout. So I wanted to see what you guys thought -- is it too soon? Does anyone know of any current ASP.NET sites in production I could tell them about or other resources that I could use to build an argument?<BR><BR>TIA<BR>DawnWell...<BR>If you are providing a service which will use .Net to run on a client machine, it may be too soon, since it'll require an additional 20 meg download for people to install the necessary support (they shoulda figured a way to ship it with XP).<BR><BR>If you are planning on building a webpage that'll run ASP.Net and use other .Net technologies, you are probably more than ok. If you are building something which will be under a heavy load and who's stability is key, there may be some wisedom in waiting for it to age slightly.<BR><BR>We aren't adopting .Net because of the first issue - too many of our clients don't want to install the .net redistributable...<BR><BR>KarlThanks for your reply. We don't need .NET on a client machine --it is just a web site (with a SQL Server backend) and they see it as being a "high perceived value, low usage" service, so heavy load should not be a problem either. I just don't see there being enough issues to where we should step back and code in regular ASP instead. (Especially since the move to .NET from ASP is not just a typical upgrade, like deciding to go from ASP 2.0 to 3.0.) <BR><BR>I know it would be ideal to wait a little longer if we could, but since we have to decide now, I felt we would be ok to move forward. Thanks again for your input.<BR><BR>Dawn<BR>No, I don't think it's too soon at all, and yes, there are *lots* of ASP.Net sites in current production....Many of them very high volume.<BR><BR>For littel insight and ammunition, I suggest that you read, and share this article.<BR><BR>http://asp.net/whitepaper/whyaspnet.aspxDawn<BR>