Hi,

yes we are using the WAP model, WPI installation isn't related to having designer files or not, it installs the compiled MonoX CMS which does't contain any designer files because they are compiled in the assembly. So if you create your own project (solution) that is based on the Web site model then you don't get designer file creating because they are created on the fly by the framework. I suppose you are using the Web site model so we will test this issue on that model too and get back to you.

Regards

Hi,

I have just downloaded the latest MonoX using WPI, opened it as a web site, added new user control, copied your code within it, built and got an error because CodeFile property in markup was not set properly.

Before:


After:


Let us now if everything is ok now,

Regards.

Greetings,
Well, unfortunately, your changes don't work. After applying your changes, and recompiling the the site, when you attempt to lunch the WebParts catalog, you get this Exception
Image #1 and the webparts catelog will not even Load.

Your Code: Will not compile and throws the exception in Image #1


My Changes to your code: notice the /. Compiles but theows the exception in Image #2

Question:
Are you able to get any poll to load with your code? If yes, can you post the code?cheers,
yousaid

Hi,

in any case when we have provided you with the code it was tested and it was working properly on our side, as you have issue with all of the samples we have provided you with is it possible to schedule a TeamViewer session related to this issue so we can check and fix everything on your side ?

Let us know if this suites you.

Regards

Greeetings,
Pick a time that works for you.
cheers,
yousaid

Hi,

does the 02.08 around the 3-5pm works for you ?

Regards

Perfect.
till then.
cheers,
yousaid

Hi,

  sorry for the delay I didn't forget about this issue but I was very busy these days. I have found the "thing" that is causing the error and it is related to Web site Project and WAP co-operation.

If you inherit UserControl / WebPart that is build on top of the WAP and you are using the Web site project type the ASP.NET has an issue related to building the control tree so that's why we don't get the control instances - they are all null.

Basically this issue is related to ASP.NET AutoEventWireup functionality and when you turn this on (and it is turned on by default)  then Web site (for some unknown reason) overrides the WAP control tree generation and controls are not instantiated. Dirty fix that I have found is to disable this functionality in case of the Web site project type so you can use the inherited WebPart (Note: at this point I didn't find issues that you may face using this fix but I'm not sure that they won't arise later on). Don' forget that If you disable the AutoEventWireup then you need to override the events such as Page_Load (OnLoad) etc.

To implement dirty fix change the below code from:

To:

I hope that this will work for you, please let us know if you need any further information.

Regards