Search:   Namespaces Discussions .NET v1.1 Feedback

AW: Tabstrip Javascript Errors Messages   Related Types This message was discovered on ASPFriends.com 'aspngwebcontrols' list. Markus hi michael, this is just a thought: i got the same behaviour when i missed to insert the webcontrol into a valid <form runat=server> tag... greetinx from germany, markus -----Ursprüngliche Nachricht----- Von: Michael Wells [mailto:Click here to reveal e-mail address] Gesendet: Mittwoch, 10. Juli 2002 01:24 An: aspngwebcontrols Betreff: [aspngwebcontrols] Tabstrip Javascript Errors OK, I'm completely befuddled. I have two, similar ASP.NET projects (A and B) running on the same server, which both use the WebControls Tabstrip. Project A works absolutely fine. In Project B, the tabstrip displays properly, but generates JavaScript errors during the page load, and doesn't function properly. (At a minimum, autopostback is broken). I'm definately using the same version of the web controls. Both projects A & B are running on the same server, and were built on the same development machine. Both projects are running as "root webs", so they use separate IP addresses. As a result, I've copied what I believe are the requisite support files from project A to project B. This includes... /webctrl_client (and all subdirs) /aspnet_client (and all subdirs) I'm also using the same registration in both A and B... <%@ Register TagPrefix="iewc" Namespace="Microsoft.Web.UI.WebControls" Assembly="Microsoft.Web.UI.WebControls, Version=1.0.2.226, Culture=neutral, PublicKeyToken=31bf3856ad364e35" %> I'm not convinced that the aspnet dir is required, but I suspect as much since it contains several *.js files. Also, I've noticed that the version specified in the directory path... /aspnet_client/system_web/1_0_3705_0 Doesn't match the version of the web controls themselves (1.0.2.226). I'm assuming that this is -not- an issue, since the control versions & directory names are identical in Project A, which works fine. Obviously, I'm using the same browser-version, on the same machine, to validate the operation of A and B... what would cause the javascript error to appear? Has anyone experienced a similar problem? Much thanks in advance. -- Michael Wells | [aspngwebcontrols] member Click here to reveal e-mail address = YOUR ID | http://www.asplists.com/asplists/aspngwebcontrols.asp = JOIN/QUIT Reply to this message...        Michael Wells Thanks Markus, While examining your suggestion, I think I just figured out what was causing the problem. Still has me puzzled a bit, but after dissecting the TabStrip-generated javascript, I came across a reference to "document.default", which was where one of the JS errors occurred. Looking at the <form> tag, I noticed that the tag had an id of "default", while the page's class name was "_default". On a suspicion, I changed the all of these symbols to "Form2"; The name of the form's class...     public class Form2 : System.Web.UI.Page { } The Inherits reference... <%@ Page language=3D"c#" Codebehind=3D"default.aspx.cs" AutoEventWireup=3D"false" Inherits=3D"re2kcorp.Form2" %> And the <form runat=3D"server"> id... <form id=3D"Form2" method=3D"post" runat=3D"server"> The error seems to have gone away. I was not aware that the <form> tag id had to match the page's class name... so I suppose I have some more reading to do. Maybe this is a limitation of the WebControls? Thanks for the tip; you sent me directly down the path I needed to explore. -- Michael Wells [Original message clipped] Reply to this message...     System.Web.UI.Page Ad MBR BootFX Best-of-breed application framework for .NET projects, developed by Matthew Baxter-Reynolds and MBR IT

Copyright © Matthew Baxter-Reynolds 2001-2008. '.NET 247 Software Development Services' is a trading style of MBR IT Solutions Ltd. Contact Us - Terms of Use - Privacy Policy - www.dotnet247.com