I required an enhanced IFrame Module that will "blur" the parameters being passed to the page referenced in the IFrame.  The issue is passing parameters in clear text is considered "bad form" by Web Inpection tools such as HP's WebInspect.  While the DNN site in a intranet site, I guess the need to "blur" the parameters does have merit. 

So I need to revise the IFrame to "blur" the parameters --  I am going to modify the parameters passed in one of two ways -- Base64 encode the value string -- this will make the effort of determining what is passed difficult for a snooper of the HTML source.  The other way will be to Encrypt the data using the standard encryption provided by .Net. 

Lastly I will offer to pass the "blurred" parameter list  as one parameter.  So once the all the paramters are assembled, I will "blur" them into one string and pass this string as a single parameter of a user provided key.  It will be the responsibility of the IFramed page to understand how to undo what I have done.  

At this point you may be asking why do all this as the IFramed page will just undo the work in javascript or other --- very true.  However, my situation is a bit different as these parameters are passed into an Active-X control as is ... so anyone snooping around ( such as HP's Web Inspect) will not see what is required to undo the blurring.

So, why the blog?  I spent most of today attempting to track down a "duplicate control" issue.  Since I used the existing DNN IFrame source basis of my module, it should have worked out of the gate -- nope!

The issue I spent more time them I want to admit related to how a Module Definition works.  There is a side effect of installing a module several times especially when you change the name of one of the pages.  I changed the name of the Module from IFrame to IFrame64 (for Base64 encoding) Unfortunately, I goofed the renaming in one version of the manifest I downloaded.  So once I corrected it, I ended up with two "edit" pages.  Now this went unnoticed for something as I thought I have screwed up the "conversion" to WAP style of implementation (IFrame does not use WAP style).  So I spent several hours poking at this issue eventually removing every control from the page.  During all this effort I was getting an error "duplicate control".  But where??  

As it turns out the incorrectly name page was still defined in the Module Definition and thus was being loaded at the same time as my correct page.  So the issue was correct and incorrect at the same time -- the correct page did not have an error, it was correct.  This root cause was the double and actually triple definition of the the "Edit" page.

Moral of the story -- if you have a duplicate control error and all "seems" correct with the page you are working on, check the Module Definition to ensure you don't have more than one page defined for a control key.

The REAL GRIEF of this is problem is I chased my tail once before on this issue and realized my problem after several hours -- as soon as I discovered my error today -- I had a flash-back to the previous issue, so I have "been there, done take before".

Hope this helps
Paul