Check this article out.

    I wish I would have stumbled across this article sooner - there is sample code included with it that implements many of the providers available in ASP.Net for an Oracle 10g database (and if you've been monitoring my blog lately, you see it's something I've been interested in).

    Is it me, or is this not the most disturbing advertisement ever? One of the single-most frightening parts of this whole operation is that it shows up in a hermetically sealed container looking like a face hugger from Aliens the movie.

    I'm starting a repository for all my public source, apps, etc. at http://www.ben-rush.net/source. I'll still post code here (and when I put new stuff up there I'll point to it from here). There's really no content yet, but there will be eventually (I have a lot of code on my machine, it's just a matter of getting around to sticking it online). A lot of it is concept code, and so you should be REALLY careful when using it - it's not tested and many bugs and security holes probably exist. Just an FYI....

    Currently the only code that's up there is rough implementation of code implementing the provider models for ASP.Net in ODP.Net. Again, concept code...so tred carefully...

    Good read for anybody - hopefully this will be a wake up call to the community.

A friend of mine came to me and wanted to know how to access members of global.asax in 2.0 (the big difference between 2.0 and 1.x is that the <script> statements have been applied to the file, which makes it feel a bit different). This is how (one odd thing I noted is that when I reference a member of this class from my code-behind, VS appears a bit behind the game on updating its internal references - therefore, intellisense appears missing and (once) the compiler failed to see my variable until I went back to the .asax file, re-saved it, and then went back to the .vb file!

Something feels almost counter-productive in this new direction taken with the .asax file, I'm not even sure why they did this....

In the global.asax file:

<%@ Application Language="VB" %>

<script runat="server">
   
    Public Shared Sub MyCallBackMethod()
       
    End Sub

    Sub Application_Start(ByVal sender As Object, ByVal e As EventArgs)
        ' Code that runs on application startup
    End Sub
   
    Sub Application_End(ByVal sender As Object, ByVal e As EventArgs)
        ' Code that runs on application shutdown
    End Sub
       
    Sub Application_Error(ByVal sender As Object, ByVal e As EventArgs)
        ' Code that runs when an unhandled error occurs
    End Sub

    Sub Session_Start(ByVal sender As Object, ByVal e As EventArgs)
        ' Code that runs when a new session is started
    End Sub

    Sub Session_End(ByVal sender As Object, ByVal e As EventArgs)
        ' Code that runs when a session ends.
        ' Note: The Session_End event is raised only when the sessionstate mode
        ' is set to InProc in the Web.config file. If session mode is set to StateServer
        ' or SQLServer, the event is not raised.
    End Sub
      
</script>

In your code-behind:

Partial Class _Default
Inherits System.Web.UI.Page

Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load
   Global.ASP.global_asax.MyCallBackMethod()
End Sub
End Class

    Keith posted some nice guides for Vista. Check them out here.

...this page will be cool.