<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://rentacoder.com/CS/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Classic ASP: Not ready for prime-time?</title><link>http://rentacoder.com/CS/blogs/real_life_it/archive/2006/03/19/448.aspx</link><description>There is a&amp;nbsp;VERY bad problem with&amp;nbsp;Active Server Pages (ASP...or what is sometimes known as "classic ASP") which prevents it from being a viable system on which to build a "big IT" project.&amp;nbsp; For 2 years we've been fighting a problem in which</description><dc:language>en-US</dc:language><generator>CommunityServer 2.0 (Build: 60217.2664)</generator><item><title>re: Classic ASP: Not ready for prime-time?</title><link>http://rentacoder.com/CS/blogs/real_life_it/archive/2006/03/19/448.aspx#453</link><pubDate>Fri, 07 Apr 2006 21:32:41 GMT</pubDate><guid isPermaLink="false">2b679553-572d-4457-89da-485055e17287:453</guid><dc:creator>pirklk</dc:creator><description>I feel your frustrations with this. &amp;nbsp;One of our internal application (ASP) has the same type of issue.. &amp;nbsp;I just wanted to say thanks though as this little tid bit of infomation was what I was looking for as a root cause of our problem. &amp;nbsp;Excellent bit of knowledge to have. &amp;nbsp;&lt;br&gt;&lt;br&gt;Thanks</description></item><item><title>re: Classic ASP: Not ready for prime-time?</title><link>http://rentacoder.com/CS/blogs/real_life_it/archive/2006/03/19/448.aspx#459</link><pubDate>Sat, 22 Apr 2006 04:57:14 GMT</pubDate><guid isPermaLink="false">2b679553-572d-4457-89da-485055e17287:459</guid><dc:creator>mariano.iglesias</dc:creator><description>Ian, I simpathyze with the hopeless sense everybody at RAC staff must be feeling now. I can imagine you may get tons of emails from coders &amp;amp; buyers demanding better web site performance. Being a RAC coder myself (&lt;a rel="nofollow" target="_new" href="http://www.rentacoder.com/RentACoder/SoftwareCoders/showBioInfo.asp?lngAuthorId=1033162"&gt;http://www.rentacoder.com/RentACoder/SoftwareCoders/showBioInfo.asp?lngAuthorId=1033162&lt;/a&gt;) I do understand the frustration of needing to upload deliverables or send status reports, while being afraid a timeout error may occur at that time. Or worst, that the financial information each coder/buyer has on the site, may be affected by poor software behaviour. However, I also know that you guys are doing the best you can, so there's no complain from our side.w&lt;br&gt;&lt;br&gt;Seeing that it's been some weeks that you are trying different Microsoft suggested fixes, what is the next step for RAC? Are you going to take the .NET road or are you planning on a complete makeover?</description></item><item><title>re: Classic ASP: Not ready for prime-time?</title><link>http://rentacoder.com/CS/blogs/real_life_it/archive/2006/03/19/448.aspx#465</link><pubDate>Wed, 26 Apr 2006 17:19:27 GMT</pubDate><guid isPermaLink="false">2b679553-572d-4457-89da-485055e17287:465</guid><dc:creator>edabdoub</dc:creator><description>Hi&lt;br&gt;&lt;br&gt;I'm a rentacoder buyer from a long time ago.&lt;br&gt;It is a great site and has helped me a lot.&lt;br&gt;&lt;br&gt;However, since .net came out (2002). I have been asking myself why you havent upgraded to .NET . Sincerelly I think that classic ASP is a pain in the a** and you can agree with that too.&lt;br&gt;&lt;br&gt;I know that RAC is a huge web application, but I supposse that you have a Data tier (SQL procedures) that will not change and come on! you have access to thousands of the best coders of the world. I think that any offshore coder (or team of coders). Could redo RAC in 1 month for less than 10,000 USD. I think it would be worth the investment.</description></item><item><title>re: Classic ASP: Not ready for prime-time?</title><link>http://rentacoder.com/CS/blogs/real_life_it/archive/2006/03/19/448.aspx#466</link><pubDate>Wed, 26 Apr 2006 22:22:07 GMT</pubDate><guid isPermaLink="false">2b679553-572d-4457-89da-485055e17287:466</guid><dc:creator>admin</dc:creator><description>Mario, &lt;BR&gt;&lt;BR&gt;Thanks for the sympathy. &amp;nbsp;ASP actually isn't the worst of our problems with the Microsoft stack (SQL Server 2005 takes that honor by a wide margin...see the other entries in this blog).&amp;nbsp; With ASP...currently the short term solution is that we've purchased 3 servers and reboot them often to prevent the memory problem from occuring. &amp;nbsp;As a result we only see this problem a few times a month, instead of many times a day. &amp;nbsp;Long term, yes we are going into .NET, because the only solution is to go forward with technology. &amp;nbsp;We were waiting until "edit and continue" was implemented (due to the loss of productivity without that feature)...and now that it has, are waiting for SP2 to get the bugs out and the release is considered stable. &amp;nbsp;Then we'll take a look at the conversion. &amp;nbsp;It will be done piecemeal to minimize risk as well as downtime to the site users. &lt;BR&gt;&lt;BR&gt;Edabdoub, &lt;BR&gt;It's a little bit more difficult than you've suggested. :) &amp;nbsp;Your off the cuff "estimate" is about 10x-20x too low. Remember that most sites are like an iceberg...you only see a small portion of them. &amp;nbsp;The main portion is all the adminitration screens that go on "behind the scenes". &lt;BR&gt;&lt;BR&gt;Ian Ippolito &lt;BR&gt;RentACoder.com</description></item></channel></rss>