{"id":37,"date":"2003-05-10T00:50:07","date_gmt":"2003-05-10T00:50:07","guid":{"rendered":"http:\/\/bdragon.com\/?p=37"},"modified":"2011-03-30T02:57:27","modified_gmt":"2011-03-30T08:57:27","slug":"asp-net-1-0-to-1-1-upgrade-issues","status":"publish","type":"post","link":"https:\/\/bdragon.com\/lair\/2003\/05\/asp-net-1-0-to-1-1-upgrade-issues\/","title":{"rendered":"ASP.NET 1.0 To 1.1 Upgrade Issues"},"content":{"rendered":"
\n

This is some technical\/web development stuff… I am just posting it up here in case it can help anyone who comes across it down the road.<\/p>\n

<\/p>\n

\nI am currently developing web sites in ASP.NET (using C# and code-behind\/VS.NET) and have been very pleased with it and the ease with which many things can be done when compared to “before”.<\/p>\n

When I upgraded my .NET version from 1.0 to 1.1 I came across some issues that I hadn’t\/haven’t seen mentioned anywhere that I could find… so just in case these can help somebody, I am putting some rambing type of descriptions here.<\/p>\n

ASP.NET 1.0 -> ASP.NET 1.1 Upgrade Issues (and fixes):\r\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<\/pre>\n
ERROR OR PROBLEM:<\/p>\n
\n
\nBizarre(?) runtime error —
\nParser Error Message: Type ‘System.Web.HttpBrowserCapabilities’ does not inherit from ‘System.Web.Mobile.MobileCapabilities’.\n<\/p>\n<\/blockquote>\n
SOLUTION:<\/p>\n
\n
\nHad to uncomment\/remove the browsercaps “result” element in web.config file\n<\/p>\n<\/blockquote>\n
COMMENTS:<\/p>\n
\n
\nDoesn’t seem to have affected\/broken anything else (so far?)\n<\/p>\n<\/blockquote>\n
<browserCaps>\r\n<!-- result type=\"System.Web.HttpBrowserCapabilities\" \/ --><\/pre>\n
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<\/code>
\nERROR OR PROBLEM:<\/p>\n
\n
\nPaging on datagrids no longer worked, though it worked before, (this also might affect “linkbuttons”? I don’t use them..) and\/or javascript errors on pages w\/datagrid or linkbuttons on them.  The source\/cause of the problem was a combination of a “template” system whereby my webforms were using a “template” class derived from system.web.ui.page and the javascript “dopostback” code that is generated to post the form to the server… I had run into this issue before with ASP.NET 1.0 when using an “autopostback” dropdownlist which wouldn’t work automatically in Mozilla until I also implemented the solution below…\n<\/p>\n<\/blockquote>\n
SOLUTION:<\/p>\n
\n
\nThe dopostback javascript “breaks” due to the fact that a control name (like “ctl0:” or “ctl0_”) is added before the server-side form tag (in the templating \/ inherit from system.web.ui.page system).  Here is a sample full html page which illustrates the problem:\n<\/p>\n<\/blockquote>\n
-------------------------------------------------------------------\r\n<html>\r\n<head>\r\n<body>\r\n<form name=\"_ctl0:frmPage\" method=\"post\" action=\"list_emails.aspx\" id=\"_ctl0_frmPage\">\r\n<input type=\"hidden\" name=\"__EVENTTARGET\" value=\"\" \/>\r\n<input type=\"hidden\" name=\"__EVENTARGUMENT\" value=\"\" \/>\r\n<script language=\"javascript\">\r\n<!--\r\nfunction __doPostBack(eventTarget, eventArgument) {\r\nvar theform;\r\nif (window.navigator.appName.toLowerCase().indexOf(\"netscape\") > -1) {\r\ntheform = document.forms[\"_ctl0:frmPage\"];\r\n}\r\nelse {\r\n\/\/this is the line causing the problem (in non-netscape browsers at least):\r\ntheform = document._ctl0:frmPage;\r\n}\r\ntheform.__EVENTTARGET.value = eventTarget.split(\"$\").join(\":\");\r\ntheform.__EVENTARGUMENT.value = eventArgument;\r\ntheform.submit();\r\n}\r\n\/\/ -->\r\n<\/script>\r\n<br clear=\"all\" \/>\r\n<table>\r\n<tr>\r\n<td><span>1<\/span>&nbsp;\r\n<a href=\"javascript:__doPostBack('_ctl0$dgData$_ctl1$_ctl1','')\">2<\/a>&nbsp;\r\n<a href=\"javascript:__doPostBack('_ctl0$dgData$_ctl1$_ctl2','')\">3<\/a>&nbsp;\r\n<a href=\"javascript:__doPostBack('_ctl0$dgData$_ctl1$_ctl10','')\">...<\/a><\/td>\r\n<\/tr>\r\n<\/table>\r\n<\/body>\r\n<\/html>\r\n-------------------------------------------------------------------<\/pre>\n
\n
\nJavascript\/dopostback doesn’t like that colon : in “theform = document._ctl0:frmPage;”<\/p>\n
My workaround\/solution involved setting the webform Name property = to the webform ID property
\n(e.g. “frmPage.Name = frmPage.ID;”) when the page is initialized.
\nThis will then output a form tag like:
\n<form name=\"frmPage\" method=\"post\" action=\"list_emails.aspx\" id=\"frmPage\"><\/code><\/p>\n
\nHere is some code which hopefully illustrates the general idea\/fix:<\/p>\n
On the .aspx page you have the form control:<\/p>\n
<form runat=\"server\" id=\"frmPage\"...><\/code><\/p>\n
…<\/p>\n
Then in the .cs (code behind file) file for the page make sure the form control is declared if not already:<\/p>\n
protected System.Web.UI.HtmlControls.HtmlForm frmPage;<\/code><\/p>\n
…<\/p>\n
Then you set up a method (I called it “pageInit()” you can call it whatever) like so:\n<\/p>\n
protected void pageInit()\r\n{\r\nfrmPage.Name = frmPage.ID;\r\n}<\/pre>\n
…<\/p>\n
Then you call this method you’ve just made in an overridden OnInit method for this page
\n(VS.NET users – this overridden OnInit is added automatically by VS.NET (I believe) –
\nif you’re NOT using Visual Studio you’ll have to add your own overridden OnInit if it’s not already there
\nand probably take out the “InitializeComponent” line shown below as well [that’s VS.NET related – for
\ndesigner support]):\n<\/p>\n
override protected void OnInit(EventArgs e)\r\n{\r\npageInit();\r\nInitializeComponent();\r\nbase.OnInit(e);\r\n}\r\n<\/pre>\n<\/blockquote>\n
COMMENTS:<\/p>\n
\n
\nThis has to be done in every page using a form (with a datagrid, autopostback or linkbutton-type controls at least..).
\nIt’s definitely a hack\/workaround, there’s probably a better solution (like solving this in the template class itself)
\n– I just haven’t had the time to look into it..  Note that I could have also included a
\n<form runat=”server”…> tag in the page template itself (so that every page is automatically a form)
\nbut this won’t work for everybody – I needed to have other non ASP.NET\/webforms forms (like a search) on pages,
\nso this solution was not a possibility\n<\/p>\n<\/blockquote>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
This is some technical\/web development stuff… I am just posting it up here in case it can help anyone who comes across it down the road.<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[43],"tags":[85,53],"class_list":{"0":"post-37","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-web-stuff","7":"tag-1-1","8":"tag-asp-net","9":"anons"},"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/peSL2o-B","jetpack_sharing_enabled":true,"jetpack_likes_enabled":false,"_links":{"self":[{"href":"https:\/\/bdragon.com\/lair\/wp-json\/wp\/v2\/posts\/37","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/bdragon.com\/lair\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/bdragon.com\/lair\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/bdragon.com\/lair\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/bdragon.com\/lair\/wp-json\/wp\/v2\/comments?post=37"}],"version-history":[{"count":0,"href":"https:\/\/bdragon.com\/lair\/wp-json\/wp\/v2\/posts\/37\/revisions"}],"wp:attachment":[{"href":"https:\/\/bdragon.com\/lair\/wp-json\/wp\/v2\/media?parent=37"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/bdragon.com\/lair\/wp-json\/wp\/v2\/categories?post=37"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/bdragon.com\/lair\/wp-json\/wp\/v2\/tags?post=37"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}