One of the features that my company is asking for is the ability to show links like "login", "Register", "logoff", "profile" as part of the links.
While building this functionality, I am finding that I need to modify classes that are in the DotNetNuke Library project. I have no problems doing this if it were to be completely external to the DNN Framework, but I wanted to get your thoughts on this prior to implementation. This would make the Links module deviate from the import because it would require a replace of the DotNetNuke.dll. This is not a good thing.
Should I duplicate some of the work that has been built into DNN and put this stuff externally as to not mess with the other items?
Is this a feature you would like to put into the DNN links component?
One other feature that is going to be put into our links component is the ability to set who can and cannot view the link. Sometimes there are requests for links but not all users should see them or they should go away once you are logged in, etc. Currently it is a see all or none. This piece will be an external object from the normal DNN framework. I am thinking that maybe both should be.
I wanted to get your thoughts on this.
Thanks