Hey Michael,

I've put a little thought into the dynamic parameters issues since I posted on your blog. So, for my company, I need to tie the DNN user to a propritary contact number stored in another database. On top of that we were moving to using ADSI to authenticate users. I was looking for a way to tie the AD user, who would be synced into the DNN database to our proprietary contact number. The solution I came up with, since we were not going to store a lot of contact info in AD was to use the zipcode field to hold our ID. So my simple modification to the IFrame was to so that the IFrame could pass the ZipCode. Now I realize to ask for the zipcode to be a parameter might sound like something that no one else is going to request.

What I'd be curious to see (and I'm still thinking about it) is a way to allow the DNN admin to select a limited set of dynamic contact information parameters. Perhaps its just a hardcoded list, for other security reasons I couldn't see using reflection to specify the object to obtain the value from.

Perhaps I'm destine to always have one off until my company can move from our psudo implementation of DNN to a full instance. (We have a lot of pages linking to our legacy ASP pages) so the IFrame is basically the most used module in our current imlpementation.

I definatly like the idea of a list of parameters that can be added to, its just a matter of adding flexibility to where the value for that parameter can come from. The pass thru parameter to set the value sounds like a pretty good idea.

Making the DNN membership/profile information avaiaible would meet my needs and I think its flexible enough. If you can also support the custom profile properties that would be perfect. I hadn't heard about that feature yet, it'd be nice to put a zipcode back into our zipcode field. :)

I agree that reflection would probably be too complicated in this situation.

Look forward to an update!