>I still have one app left on VS 2003 (.NET 1.1) as all others are new in 2.0
>A user found a problem in the app (which has been running for 10 months). It ios related to a change in new data that the app did not know how to deal with.
>
>I had to retrieve the source from VSS (have not looked at it for months). Immediately, as I expected I found I could not even run it as this runs in our Extranet secure environment with SiteMinder (a PITA program). This precludes running in development server as they do not have IIS and the user credentials for me as a developer do not match SiteMinder's access credentials that I normally tuype in a login screen. VS 2003 does not 'talk' to SiteMinder and does not give you a login dialog to change my credentials. To make a short story, this explains the main reason I moved everything (except this old app) to VS 2005.
>
>Early this morning I proceeded to convert this app to VS 2005 (C# 2.0). It is not a complex ASP.NET app, just two pages with a few controls. Took a couple of hours to convert and test. My standard MO is to disable the dll that connects to SiteMinder and establishes credentials. That way I can run it in the new VS 2005 provided Virtual IIS (localhost) and run the line-by-line debugger. Works great. Found the bug and it was easy to fix.
>
>Now I have to reconnect (uncomment) the DLL that gets the credentials so I can test in our corporate development server before I give it to the people in Production.
>
>When I run it in dev server, the parser fails with the following:
>
>Parser Error Message: Could not load type '_Default'.
>
>Source Error:
>Line 1: < %@ Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="_Default" % >
>Line 2:
>Line 3: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
>
>This is not related to SiteMinder. It is a simple stupid message from .NET that I do not understand. If I change the declaration on the default page:
>
>public partial class _Default : System.Web.UI.Page
>
>to some other name and also the corresponding "inherits" line in the aspx page, I get the same error with the new class name.
>
>What is it looking for that it does not see or cannot resolve?
>
>Any ideas?
Might it be still trying to process with 1.1? What's the version at bottom (similar happened to me once - just an idea).
Cetin
