ASP to ASP.NET II

This article documents work done on Insert Title Web Designs

Getting the Fundamentals sorted out.

I started by readng a bit of this wonderful article: http://authors.aspalliance.com/anjum/ASPMigration.aspx

Based on the information in that article I've rewritten the default.asp page from


<!--#include file="open.asp" -->
<!--#include file="xml.asp" -->
<!--#include file="close.asp" -->

TO


<%@ Page Trace=False Language="vb" aspcompat="true" %>
<%@ Register TagPrefix="oo" TagName="Open" Src="open.ascx" %>
<%@ Register TagPrefix="cc" TagName="Close" Src="close.ascx" %>
<oo:Open id="Open" runat="server" ></oo:Open>
<cc:Close id="close" runat="server" ></cc:Close>

And renamed the file from default.asp to default.aspx.

One thing I noticed is that the inclusion of aspcompat="true" led me to believe that it would be needed in order to process some of the older ASP code in these pages, but even without everything is okay so far. (leaving it nonetheless)

I've skipped the xml.asp tranformation for now, attempting to get the easier solutions in hand, first.

At the top of the open.asp page which I renamed open.ascx making it a user control I added the following


<%@ Control Language="vb" %>
<%@ Register TagPrefix="lb" TagName="leftBar" Src="leftBar.ascx" %>

And where I used to have the leftBar.asp included I replaced


<!--#include file="leftBar.asp" -->

WITH


<lb:leftBar id="leftBar" runat="server" ></lb:leftBar>

A problem arises!

At the top of the open.asp (now open.ascx) I used to have the following


<%
Response.CacheControl = "no-cache"
Response.AddHeader "Pragma", "no-cache"
Response.Expires = -1
%>

This gave me the error

Server Error in '/' Application.

----------------------------------

Compilation Error

Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.

Compiler Error Message: BC30800: Method arguments must be enclosed in parentheses.

Upon removing the offending code, which turned out to be


Response.AddHeader "Pragma", "no-cache"

all was well, but this is something I will have to return to, in order to find out exactly what ramifications it has on the caching of the pages.