Hey, sorry i didn't received these last notifications anymore. don't know why.
No fence of all this. it's just i have been given a lot of problems lately because we are now in a stage that we are making a first release of our project in production, and finally everyone here in the company starts to see what i've been doing the past 4 months ;)
I'm certenly not saying that DNN is a bad platform, although it may not be the right one for us to go further with. actually, the only "real solution" would be creating our own portal structure in asp.net. but since i'm currently still the only person on the project, we'll have to use an in-between solution. At least until I have found time to look into creating our own portal in asp.net 2.0 (any help about this is welcome).
I shoose DNN four months ago at the start of the project with very few specs of what it should be in the future. now that everyone here has thought more about it... i'm finding myself in some very strange and difficult positions :D
Maybe some more clearance about the project:
It be an internal and external support web site for our product (mobile payments). it is actually a complete re-write of a current web app which has been one of the worst things i've ever placed my eyes on. the modules are very thight integrated with our payment solution, and therefore needs to have their own place in Source Control. this is why i've been creating wrappers around DNN (such as the userinfo, modulebase, roleinfo) so we can develop the modules completely seperate and individual. We also need to have our own permissions schema according to module functionalities. Just viewing permissions on pages or modules is simply not enough. But this gives a lot of problems especially with testing the modules because you need to have a running DNN environment to test it in. Also deploying now gives problems since it doesn't fit into the way we deploy all other projects in the system.
Anyway, these are problems that we need to (and so far able to) solve as long as we don't have our own framework. wich might take a few more months if not a year. because the focus will no be more on updating and adding new functionalities than recreating the framework. and as long as i'm working alone on it, this is what will take most if not all of my time :D
We are in a progress of creating our own modules for adding users and roles etc, which than can be fully managed by us (including auditing in our database), so that we won't need to have to use DNN admin or host permissions at all. But this requires some time as well.
This is why i was asking this, because the testers here were trying to register a merchant through your Vendor modules. ofcourse merchants for us is something completely different and requires our own modules in the future to do this. also for security reasons, because the site will be used in basic form by external support team. having such a high user is not a good idea, and allowing it to do so many things that we don't use or not even know of is even worse.
clay, i'll look into that. it may indeed to do this on the production site. at least the one outside our internal network.
btw, sebastian, i'm belgian. working currently in norway ;)
Ronald