I tried it myself. First I moved the Components subdir to a new project. I compiled the project and changed all the references in the rest of the code. The problem remained. Then I replaced the 'public MasterPage()' code with the 'public MasterPage()' code from Wilson. I also activeted the commented code Joe mentions. The designer did not give any problem. Apparently the code within 'public MasterPage()' is causing the problem. I'm going to sleep now, try to continue tomorrow.

Jan

The problem appears to be in the fact that Context only exists within a HTTPContext. Because Visual Studio is a plain Windows application, there is no HTTPContext and the container cannot be created.

Adding code like

if (Context != null)

{ ...

}

arround the code within public MasterPage(), prevents the HTTPContext stuff being evaluated when used within designer. The code needs to be in a real assembly (i.e. compiled) and therefor has to be separated from the rest of the mojoPortal.Web code.

Using this, there seems to be no negative effect on the speed of the application. it looks faster, but I have only tested upto default.aspx. Still have to change the references in the other aspx modules.

Jan