Hi,

It would not surprise me if there are places in mojoPortal where using design view would have errors in the designer. I have from time to time seen these or people have reported them and from time to time I have fixed them. If you tell me specific controls or pages where you see this I will try to fix them.

However, the reason these issues creep in from time to time is because I don't use the designer at all nor do I drag and drop to create controls or pages, therefore I never notice these issues. The designer in visual studio is pretty limited under the best conditions but it does not work well with mojoPortal in general even when there are no errors, the designer will not render the same as it will render at runtime. This has everything to do with the fact that the skin/css used is determined by the skin setting on the SiteSettings object which can be resolved at runtime but not at design time because there is no http context or web request at design time.

Best,

Joe

The intellisense in source view is what I rely on, I just type <asp: and then intellisense makes it easy to find the controls and properties of interest.

But, fyi, I poked around a bit in design view and found where the ModuleTitle control was breaking design view in some places and was able to fix it. If you do svn update and rebuild it will have the latest fixes. If you do see any others let me know, I would prefer to not have errors in any design views, I just fail to notice them because I so seldom even look at design view.

Best,

Joe