Hi Ric,

I created a test form, I put some controls, I open the output window and I saw the controls listed. Now what you are saying is that "DumpControls" function is like a utility so you can copy the control names and paste them into Dreamweaver?

Let's say you have project in VS with two pages with net controls. In order to work with Dreamweaver:
would you have to create another project in Dreamweaver pointing to VS folder?
Devolopment tool is basically Dreamweaver?
Deployment will be done from VS (using copy project option)?

Thanks.

>OK, it is friday and it has been a tough week so let me see if I can explain in a clear and cohesive way:
>
>1. I create a new aspx page in VS, this will create the header, bind it tro the code behind. Save it.
>2. In Macromedia I can add all the net controls if I wish, or if you used a code automation tool like code you can tweak the controls that are already there. Of couse, it is a pain to remember the name of all the controls and objects on the page and switching back and forth from Macromedia to the aspx.cs is not too practical.
>3. I call the dumpcontrols after the page has been initialized (after the check for a postback, usually). This will put a list of all the controls on the page on the debug output area, so you can declare them and cut and paste
>
>Let me know if this is not clear enough. The best thing would be to creata a simple page, and then on the code behind just call the dumpcontrols after the postback check.