WilsonDotNet Forums : Wilson WebForm

Wilson.WebForm.Form must be used in Wilson.WebForm.Page

Mon, 21 Aug 2006 11:07:57 GMT

The page that has the WebForm must inherit from Wilson.WebForm.Page.

Thanks, Paul Wilson

Wilson.WebForm.Form must be used in Wilson.WebForm.Page

Mon, 21 Aug 2006 11:06:33 GMT

Any idea what I am doing wrong?

thanks!!!

Wilson.WebForm.Form must be used in Wilson.WebForm.Page

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Exception: Wilson.WebForm.Form must be used in Wilson.WebForm.Page

Source Error:

Line 251:					Me.Controls.Clear()
Line 252:					' set the template user control to be owned by this page:
Line 253:					Me.Controls.Add(m_Template)
Line 254:					' Now move the template child controls up to the page level so the ViewState will load 
Line 255:					Do While m_Template.Controls.Count > 0

Component Art Navbar / Multiple Forms

Mon, 21 Aug 2006 11:05:57 GMT

Your template is a user control (.ascx), and user controls cannot have the Page directive.

Thanks, Paul Wilson

Component Art Navbar / Multiple Forms

Mon, 21 Aug 2006 11:04:49 GMT

Paul,

First of all thanks for your efforts! I am STUCK big time and can't seem to locate an answer.

I am using Aspdotnetstorefront (Aspdotnetstorefront.com) inside the skin template for the site I have placed a componentart navbar. Unfortunately this component must reside between Form runat=server tags. Well due to the design of this software I cant use thier template page and use those tags. If I do I get an error telling me I cant use multiple forms.

I have tried to use your WilsonForm but I get the following error: Can you please tell me what I am missng here? I REALLY need this work around! Thanks again!

Parser Error

Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: The directive 'page' is unknown.

Source Error:

Line 1:  <%@ Control Language="vb" AutoEventWireup="false" Inherits="AspDotNetStorefront.TemplateBase" TargetSchema="http://schemas.microsoft.com/intellisense/ie5" %>
Line 2:  <%@ Register TagPrefix="ComponentArt" Namespace="ComponentArt.Web.UI" Assembly="ComponentArt.Web.UI" %>
Line 3:  <%@ Page Inherits="Wilson.Web.Page" %>
Line 4:  <%@ Assembly Name="WilsonWebForm" %>
Line 5:  <%@ Register TagPrefix="Wilson" Namespace="Wilson.WebForm" Assembly="WilsonWebForm" %>

Source File: /skins/skin_1/template.ascx Line: 3

Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42

IsPostBack = False after opening popup page

Tue, 08 Aug 2006 16:41:28 GMT

Adding:

to web.config does seem to correct the issue with postback = false when opening a popup window. However, after adding that, my other non popup window forms had postback = false.

Another symptom of the postback = false thing is that other events that should fire on a postback don't...so, for example, clicking on a button triggers the page_load, page_init...but not the clicked for the button.

Thanks for the help on this.

Use in server controls?

Tue, 11 Jul 2006 00:00:08 GMT

You'll need to send me a zip file with everything I need to reproduce and/or troubleshoot it.

Thanks, Paul Wilson

Use in server controls?

Mon, 10 Jul 2006 23:59:16 GMT

Hello,

I have had all sorts of trouble trying to get a wilson:form to work in a user control (.ascx) file. It is not using code behind. I am trying to do a nonpostback to submit the form to an action that is to a different page.

It seems that I need to inherit Wilson.WebForm.Page in the calling .aspx file, and that I am supposed to put the following into the .ascx file:

<%@ Assembly Name="WilsonWebForm" %>
<%@ Register TagPrefix="Wilson" Namespace="Wilson.WebForm" Assembly="WilsonWebForm" %>

However, it is not working. When I select from my drop down list in my form, it just goes reloads the page with my selection.

It has actually taken me quite a while to get where things seem to be setup ok, but it will not work. Help! :)

Newbie Question

Mon, 10 Jul 2006 23:58:10 GMT

I believe you mean Wilson.WebForm.Page. This sent me on a significant wild goose chase for a while about not being able to load the type (due to syntax) :(

IsPostBack = False after opening popup page

Sat, 24 Jun 2006 18:27:34 GMT

I don't recall if I tested it with and without viewstate in session to see if there was a difference -- have you tried changing that configuration setting in web.config?

Thanks, Paul Wilson

IsPostBack = False after opening popup page

Sat, 24 Jun 2006 18:26:12 GMT

Does this problem have something to do with Wilson Webform persisting the viewstate in a session variable?

Viewing Masterpages in Design View Dreamweaver MX

Thu, 27 Apr 2006 11:31:32 GMT

Dreamweaver Version 8 is now capable of displaying pages with the Wilson Matsterpage Tags

IsPostBack = False after opening popup page

Tue, 28 Feb 2006 19:01:45 GMT

Hey Marco,

Have you perhaps resolved this issue? I have the same problem and desparately need to solve this.

Regards,

Jo-Pierre

VS.Net 2005 and Wilson WebForm

Sat, 03 Dec 2005 05:46:19 GMT

Hi John:

No -- its not different. The subscriber version may have a dependency on my Library dll, which I would have removed for the other version -- but even then the code would be the same other than a small amount of structural differences.

Thanks, Paul Wilson

VS.Net 2005 and Wilson WebForm

Fri, 02 Dec 2005 15:12:38 GMT

Hi Paul,

I will look into using Reflection to get any clues. I was wondering, as part of your subscription, is the version of WebForm different from the open source one?

Thanks,
John Paul.

VS.Net 2005 and Wilson WebForm

Wed, 30 Nov 2005 05:34:34 GMT

Hmmm, I just tried and failed too. I suggest using Reflector to see how HtmlForm works in v2.0 -- that's how I figured it out in v1.*. :)

Thanks, Paul Wilson

VS.Net 2005 and Wilson WebForm

Tue, 29 Nov 2005 14:42:01 GMT

Paul,

Using your source code, could you offer me any pointers on how I could get HtmlControlContainer to render on the design surface in VS 2005? I have tried custom designers and the attribute ContainerControlDesigner to no avail.

Thank you for any direction you may offer!

John Paul.

VS.Net 2005 and Wilson WebForm

Wed, 23 Nov 2005 11:31:48 GMT

Hi John:

I barely tested it once in ASP.NET v2.0, and I don't recall if I checked the designer, so while I know it does "work" you are very much likely to be correct that something has changed in the designer. Also, as I noted in another thread, there are a lot of other additional things in ASP.NET v2.0, so I think its likely that the control won't work in all cases, although I also haven't tried to find a problem yet. Anyhow, my hope in making it open source was to both give it to a larger community, but to also allow others to work on its limitations (like the validator support). Instead I'm spending my time on the ORMapper and other issues, and while I enjoyed creating the WebForm, I've never considered it to be more than a necessary hack for a few special cases.

Thanks, Paul Wilson

.NET 2.0

Wed, 23 Nov 2005 08:15:11 GMT

I tested it once and it worked in the simple cases I tried it in, but I also think there may be some cases that it may not work in due to new cases in v2.0 -- but I haven't tried enough to know that for sure. So use with care.

Thanks, Paul Wilson

VS.Net 2005 and Wilson WebForm

Mon, 21 Nov 2005 14:49:11 GMT

Thank you for putting this control as open source. This is a nice piece of work. I have just started using this control in VS.Net 2005 and have noticed that the control does not render correctly in the designer. That is, the control does not render in the design view when I place the control in an aspx page. I am receiving an "Object reference not set to an instance of an object" error. Otherwise, the control still renders correctly in the browser; just not at design-time in VS.Net 2005. Any ideas on a fix or is this problem addressed in the subscription version?

Thank you,
John Paul.

.NET 2.0

Mon, 21 Nov 2005 06:30:18 GMT

This control works fine in .NET 2.0 ????

Not supported validation-controls - why?

Wed, 12 Oct 2005 14:36:08 GMT

Hi Paul,

thanks for the ideas.

The reason in background is the following.
We have a search-engine for full-text-search. This engine is operating in spider (http-get) mode. Now we have many different links which point to the same page-content. The links are only different in querystring.

Now we have to prevent search-engine from showing the pages twice or more. Because we have many links with different querystring pointing to the same page-content we get different action-tags for the same page (because of the querystrings). The search engine is building CRC checksums to prevent pages with the same content to be indexed twice. But the CRC checksum fails, because the action property is different, also the rest of the content is the same.

So I thought to present the search engine, no matter what the querystring ist, always the same action string. So the CRC-checksum would be the same and the pages are indexed only once.

Hopefully I explained my problem clearly.

Thanks
Juergen

Not supported validation-controls - why?

Wed, 12 Oct 2005 06:21:26 GMT

Is that the only reason you want to change the action -- just for spiders? I'm also curious why that would matter, if you don't mind sharing, although that's certainly your business. Anyhow, if that's the only issue (changing the action for just spiders) then you are probably better off just overriding the render method and altering the rendered html before it is sent to the browser -- maybe testing for the spider first so that you don't waste resources doing that for the other cases. If you don't know how to do that, see the source code for the WebForm, since it already does that for some other reasons.

Thanks, Paul Wilson

Not supported validation-controls - why?

Wed, 12 Oct 2005 05:53:16 GMT

Hi Paul,

thanks for the explanation. But for your solution I still have to use the built-in form for the page-form or?

Background:
I have one big form in my pages and I need to set action attribute to some value if the request is from e.g. googlebot or any other spider. I cannot set the action with the build-in control, so I thought of using your controls - but they don't support validation controls.

Do you have an idea how I can deal with that problem?

Thanks
Juergen

Not supported validation-controls - why?

Tue, 11 Oct 2005 02:53:51 GMT

Hi Juergen:

The problem is that the ASP.NET framework just assumes far too much that there is going to be just a single form. I was able to get around that on the server-side by requiring a new base page that overrode some of that. But on the client-side, where validators have a lot of javascript, that single form assumption was just too much. At one time I put a lot of work into trying to rewrite some of the validation javascript, but in the end it just didn't happen. Maybe someone better with javascript could make it happen, but it was definitely not trivial. The validation logic on the server meanwhile was something solvable, but even there it was very questionable since it required using reflection to change private members. Finally, keep in mind that you can continue to use the one single built-in server form, with validators, while still using the WebForm for smaller "side" forms without validators -- so you don't have to give up validators for the main form.

Thanks, Paul Wilson

Not supported validation-controls - why?

Tue, 11 Oct 2005 00:16:51 GMT

Hello,
just a question concerning the problem that validation-controls are not supported.

Where does the limitation comes from or what is the reason that they are not supported?

Thanks
Juergen

Viewstate Bug

Mon, 26 Sep 2005 04:14:08 GMT

Hi Matt:

Viewstate is certainly present in my test, although it may be an empty viewstate if there's no state to save. And the button click event does fire in my test too, so you'll need to send me more details if you are seeing something else.

Of course there is a well-known and very old IE browser bug that means the enter key does not post the button id when it submits a form with a single textbox -- but that's not related related to the webform in any way -- its just IE.

Thanks, Paul Wilson

Viewstate Bug

Sun, 25 Sep 2005 17:17:08 GMT

Hi Paul,

Love the control! I just wanted you to confirm whether or not this was a bug in Wilson WebForm. If you create a web form which contains only a textbox and a button, then no viewstate is present. The absence of the viewstate prevents the button click event from firing.

I looked into the source code, and it appears that if you are using the EachInstance viewstate storage method, that you check for the presence of the "__doPostBack" function to determine if the viewstate should be outputted. The problem as far as I can tell is that the standard server-side form will only output the "__doPostBack" function if required, and since a button will submit without the presence of this function, it is not written.

Thanks,

Matt Cox

IsPostBack = False after opening popup page

Thu, 18 Aug 2005 05:55:06 GMT

I tested it only on IE and FireFox, not Opera. :) You'll really need to email me a set of code that reproduces this.

Thanks, Paul Wilson

IsPostBack = False after opening popup page

Thu, 18 Aug 2005 00:31:20 GMT

Hi Paul,

I found out something else: it seems that the behavior I described happens mainly with what I'm currently using as the "main" browser, Internet Explorer 6.0.2900.2180.xpsp_sp2_rtm.040803-2158 (it's a Service Pack 2 on Windows XP Professional) and with Mozilla FireFox 1.0.2.

I've tried, for example, with Opera 7.54 and it works fine... I don't know if this can give you a clue as to what might be the cause...

Thanks,
Marco

IsPostBack = False after opening popup page

Thu, 11 Aug 2005 12:57:00 GMT

Thanks Paul - it's really strange because when I do it I always get the kind of behavior I wrote about...
Anyway, I'll see if I can figure something out and maybe I'll get back to you if I have more information.

Thanks again,
Marco

IsPostBack = False after opening popup page

Thu, 11 Aug 2005 10:49:16 GMT

Yes, I tried it every order I could think of. I have seen things that involved popups sometimes being cached by the client browser unless I went out of my way to code it to never allow that -- but this didn't look like one of those cases to me either.

Thanks, Paul Wilson

IsPostBack = False after opening popup page

Thu, 11 Aug 2005 09:46:53 GMT

Hi Paul,

did you open the popup page (hyperlink to a home.aspx with target=_blank) before clicking button1?

IsPostBack = False after opening popup page

Wed, 10 Aug 2005 11:05:52 GMT

Hi Marco:

I took your code and could not duplicate it. If you continue to have this problem then you'll need to send me the code that reproduces it since I cannot.

Thanks, Paul Wilson

IsPostBack = False after opening popup page

Wed, 10 Aug 2005 09:58:02 GMT

Hello,

I have a strange problem with all pages derived from Wilson.WebForm.Page.
In these pages, everything seems to work fine except after opening a popup page (via JavaScript or a link with target=_blank). In these cases, the first time a form button is pressed after opening the popup, the effect is that the page is reloaded but IsPostBack is False. If you press a form button a second time, everything starts working correctly again...

Any ideas as to what could be causing this strange behavior?
Just to give you an idea, this is the body of a test page I've created:

<body MS_POSITIONING="GridLayout">
<form id="gino" runat="server">
<div id="pino" runat="server" />
<asp:Button id="Button1" style="Z-INDEX: 101; LEFT: 384px; POSITION: absolute; TOP: 192px" Text="Button"
runat="server" Width="144px" Height="24px" Font-Size="Small"></asp:Button>
<asp:TextBox id="TextBox1" style="Z-INDEX: 102; LEFT: 384px; POSITION: absolute; TOP: 152px"
runat="server" Width="136px" Height="24px"></asp:TextBox>
<asp:HyperLink id="HyperLink1" style="Z-INDEX: 103; LEFT: 400px; POSITION: absolute; TOP: 104px"
runat="server" NavigateUrl="Home.aspx" Target="_blank">HyperLink</asp:HyperLink>
</form>
</body>

And this is the code-behind class:

Public Class Test
Inherits Wilson.WebForm.Page

#Region " Codice generato da Progettazione Web Form "
Protected WithEvents Button1 As System.Web.UI.WebControls.Button
Protected WithEvents TextBox1 As System.Web.UI.WebControls.TextBox
Protected WithEvents HyperLink1 As System.Web.UI.WebControls.HyperLink
Protected pino As HtmlGenericControl
Protected gino As HtmlForm

'Chiamata richiesta da Progettazione Web Form.
<System.Diagnostics.DebuggerStepThrough()> Private Sub InitializeComponent()

End Sub

'NOTA: la seguente dichiarazione è richiesta da Progettazione Web Form.
'Non spostarla o rimuoverla.
Private designerPlaceholderDeclaration As System.Object

Private Sub Page_Init(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Init
'CODEGEN: questa chiamata al metodo è richiesta da Progettazione Web Form.
'Non modificarla nell'editor del codice.
InitializeComponent()
End Sub

#End Region

Private Sub Page_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
'Inserire qui il codice utente necessario per inizializzare la pagina

If IsPostBack Then
pino.InnerText = "POSTBACK!"
Else
pino.InnerText = "no postback"
End If

End Sub

Private Sub DataGrid1_SelectedIndexChanged(ByVal sender As System.Object, ByVal e As System.EventArgs)

End Sub
End Class

Thanks for any help or information on this...

Bye,
Marco

Viewing Masterpages in Design View Dreamweaver MX

Wed, 13 Jul 2005 20:50:01 GMT

We just redesigned a website www.finalemusic.com using MasterPages and a combination of VS.NET and Dreamweaver. The trick was creating a design-time css tag that isn't written at run time (visible="false" attribute) and making sure it is the first tag in the page. I suspect that if Dreamweaver doesn't recognize the first tag it doesn't render the design view.

For example:
<link id="designcss" href="/FinaleMusicNew.css" type="text/css" rel="stylesheet" runat="server"
visible="false"></link>
<Wilson:MasterPage id="MasterPage1" runat="server">
</Wilson:MasterPage>

The real stylesheet is in the MasterPages template. I tried importing the tags in Dreamweaver, but I don't think that had any effect. The closing tag </Wilson:MasterPages> still appears at the bottom of the page, but we chose to ignore it.

On a side note, I hope that Macromedia improves Dreamweaver's ability to work with VS.NET in the next release. Unless VS.NET 2005 IDE is vastly improved we will still use Dreamweaver for the design work.

Andy

Viewing Masterpages in Design View Dreamweaver MX

Wed, 29 Jun 2005 07:30:26 GMT

I can only hope someone with DreamWeaver experience can help you as that is out of my realm of experience.

Thanks, Paul Wilson

Viewing Masterpages in Design View Dreamweaver MX

Wed, 29 Jun 2005 06:52:31 GMT

Well it seems to be only with the Master Pages. Commenting out for instance it I comment out the following tag and it's closing tag,
<WILSON:MASTERPAGE id="MasterPageAboutUs" runat="server" templatefile="~/Company/Layout.ascx">

will allow me to view the page in design view.

Newbie Question

Wed, 11 May 2005 12:45:12 GMT

My first thought is that you still need to add the inherits="Wilson.Web.Page" attribute to your @Page declaration (or set the base page type in the web.config file for the whole site). If that doesn't fix it then let me know and I'll debug it myself.

Thanks, Paul Wilson

Newbie Question

Wed, 11 May 2005 12:02:20 GMT

Hey all,
I am just beginning to learn ASP.NET and how it works, and I want to use the WilsonWebForm.dll in my aspx file (specifically <Wilson:form ). The aspx file does not use codebehind, so all the scripting and html are in the same file. I have only the WilsonWebForm.dll in my applications /bin folder, and this at the beginning of my .aspx:

<%@ Import NameSpace="System.Data" %>
<%@ Import NameSpace="System.Data.SqlClient" %>
<%@ Import NameSpace="System.Collections" %>
<%@ Import NameSpace="Wilson.Web" %>

<%@ Page Language="C#" Debug="true" EnableViewState="false" %>
<%@ Assembly Name="WilsonWebForm" %>
<%@ Register TagPrefix="Wilson" Namespace="Wilson.WebForm" Assembly="WilsonWebForm" %>

And of course I get an error:

File or assembly name WilsonWebForm, or one of its dependencies, was not found.

I have no idea what I'm doing wrong, and I've been scouring the web for instructions, but to no avail. Any help is appreciated!

Unwanted view state in server form

Tue, 15 Mar 2005 03:50:44 GMT

Hi Adrian:

Unfortunately, ViewState is a page-wide concept, since MS didn't really plan for multiple forms, so I have to handle one page-wide ViewState the same for all forms on the page. I created two ways to handle it, and planned a third I never implemented -- one way was to copy the ViewState into each form (sounds like what you're using), and the other was to put it into Session (not always good option, but for smaller sites it works great). I was hoping to also only have ViewState once on the page and use JavaScript to post it back in all forms -- I never got to this though, and it would have been somewhat browser dependent anyhow.

Thanks, Paul Wilson

Unwanted view state in server form

Mon, 14 Mar 2005 21:08:41 GMT

Hello Paul

I've been using your WebForm for quite a while, but I have one problem that is still plaguing me. For a variety of reasons, I have a number of pages that have a degenerate server-side form in addition to a number of Wilson forms. Essentially, I do this because I need some of the functions of the form to dump client-side script out - startup scripts. Unfortunately, I seem to get the viewstate for the whole page dumped as well - even though there's nothing in the form at all. Any idea what's going on here? Is there a way to suppress that viewstate - the important bits of which I already keep in session state for the Wilson forms??

Thanks

Adrian

Triggering Unwanted validators

Mon, 07 Mar 2005 09:22:42 GMT

That worked great! Thank you very much!

Triggering Unwanted validators

Mon, 07 Mar 2005 04:39:19 GMT

There's a long standing bug in IE that makes the enter key not submit a form with a single textbox. There are lots of hacks that have been developed that you can find it you search, but the easiest is to put a second hidden textbox in the form. Other solutions typically involve lots of javascript to try to trap the enter key.

Thanks, Paul Wilson

Triggering Unwanted validators

Mon, 07 Mar 2005 02:19:07 GMT

First of all, I would like to thank you for the great component.

Here is my situation. I have a page with 3 forms; one for login, one as a main form, and another single-textbox form for referring other users. The login form and the referrence form are Wilson forms. The login form works fine and so does the main form. But the referrence form does not execute when ENTER is pressed, but works when the submit button is clicked. I tried some things and I've discovered that it is causing some validation error with the main form. There are no validators in this page and all submit buttons are set not to CauseValidation.

Setting Focus

Thu, 13 Jan 2005 17:57:51 GMT

It looks like I reference UniqueID -- it should be ClientID instead:
http://www.wilsondotnet.com/Code/?path=Templates&file=PageBase.cs

Sorry about that, I have it fixed on other client sites that are more complex, but I missed it on this one.

Thanks, Paul Wilson

Setting Focus

Thu, 13 Jan 2005 07:34:32 GMT

Paul, in your method WriteFocusScripts() you create dynamic javascript for setting focus:

registerclientscript(focusControl.id + ".focus();"

(not exact I know, but you get the idea)

The problem with that code is that the javascript that it spits out looks something like this:

LoginBoxes:txtBoxLoginID.focus();

I'm trying to set the focus on my login screen which is in a content region called "LoginBoxes." So, javascript blows up on the ":" character b/c ASP.NET outputs the name of the control to be: LoginBoxes_txtBoxLoginID. I had to modify the code to replace the ":" with "_" in order for it to work. My question is, why does it work for you this way?

Thanks

Viewing Masterpages in Design View Dreamweaver MX

Mon, 06 Dec 2004 12:53:20 GMT

Is this just about MasterPages? Or also about my WebForm component? Either way I don't know anything about using Dreamweaver, but knowing for sure which one you are referring to may help someone else answer this.

Thanks, Paul Wilson

Viewing Masterpages in Design View Dreamweaver MX

Mon, 06 Dec 2004 12:07:18 GMT

I've been searching the ends of the earth trying to work out this problem. We had a site developed by a third party that utlizes the WebForm Masterpages.

When I try to open these pages in Dreamweaver all that is displayed is the ASP icon so I can do no editing of the page in design view unless I comment out the masterpage tags while I work on them and remember to uncomment them before moving into production.

I've tried a number of configuration changes in Dreamweavers Tags.xml, TagLibraries.vtm but to no avail.

I've also been able to work around this if I do not define the site in Dreamweaver but I lose the functionality of the Source Control working with it in this manner.

I've imported the wilson tags into the Tag Libraries.

I'm unable to find much documentation that is clear in getting Third Party Tags to behave in a a specified manner from searches.

Has anyone had a similar experience and found a way to work in design view of Dreamweaver with these tags?

Use in server controls?

Tue, 09 Nov 2004 04:27:17 GMT

Sure, you can use any control in a custom control, and the WebForm is no different in that regard. It is a little different though in that you can't put a form inside another form, so you may have users of your custom control getting errors if they try to put it in their own form.

Thanks, Paul Wilson

Use in server controls?

Sun, 24 Oct 2004 14:56:57 GMT

Is it possible to use these forms within a server control, or must they be in an ASPX page?

Thanks,
Steve