Mitch,
What I'm attempting to do is create a module that has absolutely no UI. I'm not sure if a FriendlyURL or an HTTP Module are "examples" of non-UI modules that can be "replaced". If they are, then something like this would be an example.
Every example I've noticed assumes we have .ascx controls, and we have access to Entities.Modules.PortalModuleBase.
Let me use an example, it's not actually what I want to write, but is a good example.
One of the items "management" has wanted for many years is a "filter" for data passed into our website. (Yes, I know, there are a LOT of hardware based filters... But bare with me in my example...)
To implement a filter, I'd write an HTTP Module. One item I'd want to do, to keep performance up, would be to restrict the data the HTTP Module would process. It should be possible to restrict what my module processes based, for example, on ModuleId and PortalId. These fields are not quickly available to the HTTP Module.
Lastly, how would I build an install package that includes my HTTP Module into the system. The examples I see, all implement my module on top of an active DNN site, and use DNN itself to build an install package. If I'm an independant developer, it would be really nice to do my development without altering my "reference" copy of the installed DNN on my development machine. The installer allows me to install and test the finished product.
Are there any examples of developing FriendlyURLs or HTTP Modules?
Thanks!
Bob