ASP.NET Global.asax??

[Frank Smith]

Documentation is kind of weak.... if global.asax is "like" global.asa, can a
global.asa be copied and renamed to work as a global.asax?
Embedded in global.asa is a reference to itself so I changed it to
global.asax, saved it as a global.asax and sent it to the server. So now on
the server I have both global's.

Created a simple test pgm to "tinker with ASP.NET" with a DBR just reading
an existing file (that is also defined in global.asa), on running get an
error:

Runtime Error
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.

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".

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>


On Publishing, I also sent along web.config and the entries in _fpclass.....
anything else go up there?

 

[Kevin Spencer]

The global.asax file is "like" the global.asa file in the same way that a
BMW engine is "like" a VW engine. But put a VW engine into a BMW, and the
same sort of thing will happen. I would suggest going to http://www.asp.net
for starters.

ASP.Net performs similar things to ASP in a very general way, but the
internal structure and design of it is entirely different. Get ready for a
long haul on the big learning curve. Bring lots of sandwiches.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
A watched clock never boils.

 

[Frank Smith]

I do not have a lot of sandwiches.
Did get a simple read DBR to work in .NET and found out that I did not need
a global.asax

Interesting though, after I posted and ran the page, I made some local
updates and re-Published the page.
The OLD page keeps showing up even though I verified the date/time stamp on
the new one.
Anything else that I must send up with the new page?

 

[Kevin Spencer]

http://www.msdn.microsoft.com/office/understanding/frontpage/infocenter/aspnet/default.aspx

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
A watched clock never boils.