http://forums.asp.net/t/296012.aspx/1?Single+Page+SiteWed, 06 Aug 2003 19:59:53 -0400296012296012http://forums.asp.net/p/296012/296012.aspx/1?Single+Page+Site Anyone have experience converting a classic ASP Single Page Site (where navigation is done with QueryString variables instead of html or asp files) to dot-net? Our single-page-site is quite large and includes both vbscript and javascript on the server side with client-side javascript for certain functions. We are currently running NT4 server with IIS3 and SiteServer4 all service packs applied. We're using LDAP and forms authentication for personalization. We're using AdManager to rotate ads and keep track of views and clicks. Anyone have any experience with this? TIA 2003-07-31T16:12:53-04:00298068http://forums.asp.net/p/296012/298068.aspx/1?Re+Single+Page+Site well, first thing you'll need to do is upgrade your server ;-) really, I couldn't comment without a clearer idea of the current site and your objectives for the upgrade. 2003-08-02T07:26:54-04:00299348http://forums.asp.net/p/296012/299348.aspx/1?Re+Single+Page+Site Hmmm. Upgrade server? Now why didn't I think of that ;~} I'm trying to get a feel for how much effort it's going to be before the server upgrade ($$$). The main objective for the upgrade is to get back to a server and IIS version that Microsoft will be continuing to support in the future. If Microsoft would continue to support SiteServer on NT4, we probably wouldn't be making the change. HOWEVER, we have had performance and uptime issues that -- according to Microsoft -- would be solved with .Net. Thanks, Owen 2003-08-04T16:31:14-04:00299900http://forums.asp.net/p/296012/299900.aspx/1?Re+Single+Page+Site If you don't have much $$$$, problem I would suggest to upgrade the hardware/software. May be to upgrade you might have to put some affort, but later, that makes your life easier. Since you mentioned about performance, without changing any code, if you move to win2003, it gives lot better performance!! (Because of IIS move one layer down!!) 2003-08-05T02:25:14-04:00301831http://forums.asp.net/p/296012/301831.aspx/1?Re+Single+Page+Site Not that we don't have much $$$, just that the $$$ have not come up in the budget yet. Next quarter.... 2003-08-06T18:58:13-04:00301911http://forums.asp.net/p/296012/301911.aspx/1?Re+Single+Page+Site We're in the process of doing a similar conversion right now & we're encountering a lot of issues. We have two well trained ASP developers onsite, and got a functional ASP.NET site built using server.execute on the files we'd turned into .ASPX files. In the conversion of the files we simply moved the language to VB.NET and switched our recordsets to ADO.NET from standard ADO. In doing this though we couldn't really take full advantage of most of the new .NET functionality (datagrids and databinding) as postbacks to forms that were running through server.execute forced the files to execute on their own w/out the container page. The site is sort of a "hybrid" not truly using or getting the benefit of any of the more powerful tools in .NET, but as I mentioned, it is functioning. Prior to this setup we tried creating a page with a single server form where the pages being loaded no longer through server.execute, but as registered ASCX controls inside a placeholder, but this caused a number of problems and ultimately failed to provide all the functionality that was part of our Classic ASP application; they "hybrid" application was ultimately more successful than this solution. All that being said, we have decided to hire in an ASP.NET consultant to help re-architect the site. A lot of the functionality of the old site will have to be constructed by modifying the system's base page class, and our Classic ASP developers just aren't quite up to this yet. Though having Visual Studio.NET onsite now is a little more conducive to this type of development. In any case I hope this has helped. 2003-08-06T19:58:36-04:00