Has there been any progress on this? This continues to be a problem for us. The grid control's and other controls work, but the designer is useless. We have to do all the coding in the markup, or create the page in another project that lacks the Web Client Software Factory and then copy over the markup. It's a real pain.

Thanks for the follow-up. I am currently trying to figure out all problems related to WCSF and probably come up with a guide/tutorial that could probably be helpful in the future.

Thanks for the additional information - I will bury the controls several levels down the structure and see how  the stock AJAX or WARP can interfere with them. I will also play with AppStylists.

If you have some specific information on the setup that would make it easier for me to reproduce that - it will be much much appreciated.

Thanks for taking the time to look at this

Yes, copying ig_res locally for the sample WCSF project works for the runtime – however, I already had it in the existing project.  The WebDialogWindow in my project is (was) a few layers down, and it was having difficulties with AJAX async post-backs (AJAX extensions or WARP)
It was also causing problems with AppStylingManager  - when dropped on a page that is utilizing AppStylist, the style gets clobbered.  Have several issues with this after a WARP postback though...

Hello Guys,

First of all, I'd like to apologize for not responding on time to the original question. Please, excuse us for that.

I went through the pain of installing WCSF for VS2008 and created a new project. I was able to reproduce the design time error you reported - I guess that the WCSF template does not add by default a reference to an assembly the designers need. I will check this out in details and write you later.

At runtime I was able to get WebDialogWindow working in WCSF - please, see the screenshot attached. The key is to copy the ig_res folder locally - it contains resources such as images and styles for dialog window that are needed and it appears that this is the default setting of the control in this environment (as opposed to using the global virtual ig_common folder).

Please, let me know if this is enough to get you started - I will of course investigate everything in detail, I just want you guys to get started and working asap.