I am passing the variables from the main VWG form into the VWG popup form. These are properties of the VWG popup form. I suspect this is as secure as the session variable way of doing things because it is internal to VWG. One of the properties passed is a GUID. Since it is VWG that is passing it, I believe there is no way to sniff out a GUID. Is this clear? Is it clear how I am passing the variables? If this is in HTTPS, can the page be intercepted somehow, and somehow is there a way to not introduce new parameters, which I am not worried about, but is there a way for a hacker to see the VWG properties that were passed into the popup form, and then read by the aspx page? I read the variable from the popup form properties with this code... can you tell me if there are holes in this?
Dim f As UploadAurigma = DirectCast(Me.PageContext.Parent, UploadAurigma)
somevalue = f.MyVariableFromVWGPopupForm
I am not able to relate the usage of AspControlBoxBas, AspPageBox and AspPageBase to the practicality of how they are used. Is one used with the asp.net wrapper? Is one used with custom control? And the AspPageBox is used to simply load in an aspx page with the path property? I see that AspPageBase is used in the aspx page to inherit from VWG, so I can read variables like I do in the above code. I really need this stuff cleared up for me.