Sorry if i sound like an idiot - it's been years since I worked with an iFrame. As i recall the width and height were passed on the creation of the iFrame. Do you want the iFrame to: 1) Determine the size of the container that is holding it. 2) Use the size discovered in step 1 to resize itself to expand to fill it's container. -ward

Sucharita is right, you will have to get an SSL cert, install the certificate on your web server, and then use HTTPS:// to encrypt the traffic between the client's browser and your web page. This is easy stuff, and most places that sell SSL certificates have step-by-step instructions of how to set this up. -ward

Hmm, interestingly enough, there is an article on this right here on The Code Project. http://www.codeproject.com/aspnet/IFrameParams.asp Also, a quick google search on "asp.net iframe parameters" yielded quite a few hits that seemed very relevant. -ward

CybrWeez wrote: I've tried vsdraCOM and vsdraCOMRelativePath These two settings only do any magic if the assembly is designed to work through a CCW (Com Callable Wrapper). Basically, if you have designed your assembly to be a COM component. I have used these settings with success. I found a great .NET pdf library that I needed to use in VB6, so I wrote a wrapper object that looked like the VB6 printer object. Using attributes to control the visibility of my properties and methods, then using CCW to expose the object to the COM world. Worked great. :-D In the project properties of your source project (Not the deployment project), check the "Register for COM interop" to get the TBL built, etc. Also, using the various attibutes can make your assembly look much better to those COM eyes... Imports System.Runtime.InteropServices ' Expose this object as a COM object _ Public Class PDFPrinter ' Content Goes Here End Class Then, in the deployment project... [cPDFWriter.tbl] Register=vsdrfCOM [cPDFPrinter.dll] Register=vsdrfCOM