Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0How to protect global.asax.vb during DNN upgradesHow to protect global.asax.vb during DNN upgrades
Previous
 
Next
New Post
9/21/2009 4:23 PM
 

We have added the event handler Application_AuthenticationRequest to the global.asax.vb file to create a cookie for single sign on for a legacy app.  It works nicely.

Each time we upgrade DNN, the global.asax.vb file is replaced and our single sign on breaks.  Is there a way to keep this method from being overwritten or a better way of attaching to the event? 

I am afraid that someone (probably me) will do an upgrade and won't remember to copy the method back and single sign on will stop working.  All suggestions appreciated.

We are currently on DNN 5.1.2.  Thanks in advance -

Ted

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0How to protect global.asax.vb during DNN upgradesHow to protect global.asax.vb during DNN upgrades


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out