.NET, ASPX, and a small pocket book....

[Jazzpak]

I cannot currently afford to buy Visual Studio .NET, Windows 2000, on a new computer that must have a sizable processor, a large RAM chip...512 would be best, and a DVD rom for the .NET software.<BR><BR>Price for all is about $4000 and change.<BR><BR>I would like to start displaying a little knowledge of the tchnology buy creating several .aspx files on my site. The problem I am having at this point, is how to display errors. This is the error message I get on a page I am creating.<BR><BR>Server Error in '/' Application.<BR>--------------------------------------------------------------------------------<BR><BR>Runtime Error <BR>Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. <BR><BR>Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".<BR><BR><BR><!-- Web.Config Configuration File --><BR><BR><configuration><BR> <system.web><BR> <customErrors mode="Off"/><BR> </system.web><BR></configuration><BR> <BR><BR>Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.<BR><BR><BR><!-- Web.Config Configuration File --><BR><BR><configuration><BR> <system.web><BR> <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/><BR> </system.web><BR></configuration><BR> <BR>-----------------------------------------------<BR><BR>I just returned from iNNERHOST'S/Homnick Solution's .NET Developer seminar in Miami where I was limited with time discussing the problem with techs for iNNERHOST. How do i get to these errors? How do I show what's wrong with my code?<BR><BR>I have...<BR><BR>home pc, editing in an HTML editor.<BR><BR>no framework installed on my home system.(do I need it to show these errors?)<BR><BR>my site is on windows 2000 and has all .NET compatibilities.<BR><BR>Do I need to Compile this new aspx file on my home pc before I send it to my site? Or, does a simple aspx file get compiled by windows 2000?<BR><BR>Any info on this subject I truly would value.<BR><BR>Thanks,<BR><BR>Tim<BR>I had the same problem and solved it by blindly following the directions they supplied in the error message.<BR><BR>1. copy the following lines of code into a word processor like Notepad:<BR><BR><!-- Web.Config Configuration File --><BR><BR><configuration><BR><system.web><BR><customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/><BR></system.web><BR></configuration><BR><BR>2. Save it with the name "web.config" into the root directory of your website. For example, I could have several websites set up under IIS with the following folder names: WebSite1, WebSite2,.... Say that 'WebSite2' has asp.net pages as part of the site. I would save this 'web.config' file in the 'WebSite2' folder.<BR><BR>3. That's all I had to do. Very simple.OK!!<BR><BR>Progress...<BR><BR>I did as you say and now have a new dilema!<BR><BR>I get redirected to this URL:<BR><BR>http://www.sit-rep.com/mycustompage.htm?aspxerrorpath=/test.aspx<BR><BR>How do I now display the errors in my page? (test.aspx)Can't help you on that one. Once I made the change I sent you everything worked the way it was supposed to work and I was able to view the errors on my pages. Sorry.