Sounds like one of the old Pre-VS Wizard web sites.
I'd be happy to have a look at it and offer suggestions. Myself - web developer since pre-Denali (first release of ASP) so I know my way around some of the early technologies. Let me know if I can help Dave ******************************************************************** David J. Boccabella Proprietor Anubis Systems Phone: 0433 808 525 Fax: 3200 0085 Email: <mailto:[email protected]> [email protected] This e-mail and it's contents is confidential to Anubis Systems. This e-mail, any attachments, or any part of can not be reproduced without the express written permission of Anubis Systems ******************************************************************** From: [email protected] [mailto:[email protected]] On Behalf Of Peter Maddin Sent: Wednesday, 21 December 2011 2:32 PM To: 'ozDotNet' Subject: RE: ASP.NET web site I have got a response back from the author of the web site I am trying to investigate In short no it was NOT written in ASP and converted. This was however one of the first .Net Projects I undertook so it looks very similar to ASP style of programming. The code has never been compiled but placed AS IS on a web server. Again a habit from writing ASP for years before It targets .net framework 2.0. The aspx pages are a mixture of VB, Javascript and HTML. I have managed to get it registered in IIS 5.1 (old XP Pro desktop) and get the default.aspx page open. I can open it with vs2005 (installed specially for this purpose) as a web site. I can debug to a limited extent after attaching to aspnet_wp.exe. However many of my breakpoints cannot be hit (although some are?!). For most I get a circle with an exclamation mark and the message "breakpoint will not currently be hit no symbols loaded for this document" If I get an exception or if application logic is directed to a web page, breakpoints are ignored, so I just get the standard asp.net error page. If I try and build the web site (there is no project or solution files) I get build errors. Without being able to build in debug mode I would guess that there are no PDB files so no symbol information. I have never tried to work with anything quite this old. That this is even possible (no compilation) has surprised me. I am not sure how the author managed to debug this web site. Any ideas short of scrapping it and rewriting to try in order to debug it would be most welcome. Regards Peter Maddin Applications Development Officer PathWest Laboratory Medicine WA Phone : +618 6396 4285 (Monday, Wednesday,Friday) Phone : +618 9346 4372 (Tuesday, Thursday) Mobile: 0423 540 825 E-Mail : [email protected]; [email protected] The contents of this e-mail transmission outside of the WAGHS network are intended solely for the named recipient's), may be confidential, and may be privileged or otherwise protected from disclosure in the public interest. The use, reproduction, disclosure or distribution of the contents of this e-mail transmission by any person other than the named recipient(s) is prohibited. If you are not a named recipient please notify the sender immediately. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Ken Schaefer Sent: Wednesday, 14 December 2011 3:58 PM To: ozDotNet Subject: RE: ASP.NET web site Definitely a converted ASP application (plenty of articles touting how easy it as to convert ASP to ASP.NET by tweaking a bit of syntax back around 2001/2002). This type of page is the result. The use of ADODB and adovbs.inc is a give-away Cheers Ken -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Peter Maddin Sent: Wednesday, 14 December 2011 3:55 PM To: [email protected]; 'ozDotNet' Subject: RE: ASP.NET web site Thanks >> Yeah that is a 1.1 vb web page I suspected as much. >> looks like it was either a wizard conversion from asp to asp.net, It does look like a converted asp application. I actually checked out some asp examples in order to compare asp code with what I was looking at. >> Try turning option explicit off and option strict off in the project properties. I'll give that a try. >> My first reaction, is scrap it and rewrite I could not agree more but the powers that be would prefer one to maintain what's there and avoid a rewrite if possible. >> Which is the reason I decided not to do vb.net and do c# instead. I also decided not to use vb.net and go with C#. Have not regretted that decision until I was landed with this.
