I would like to change some functionality in a core file (in library\controls) of the source package. How would I go on doing that in a "best practices" manner? I belive that it would be best to leave the vb-file as it is to make it possible to upgrade the whole package to newer versions in the future, but at the same time I need a function in that file do it's thing in a slightly altered way.

In short: I want to use some altered behavior of this file WITHOUT breaking anything, comes to future upgrades. How?

I currently use DNN version 4.6 running on my XP Pro dev machine (VS 2005/2008, MS SQL 2005). I have some C# knowledge but are not that used to asp.net.

Thank you for your answer Ian. This does sound like a good approach to me.

I imagine that I could also extend the pagingcontrol-class (creating my own control that inherits and overrides). Maybe that's not always a good solution - if the base class is changed in newer releases, it might require some rewriting - so I think what you suggested is better.

/Cendion