We have recently upgraded all of our WebForms projects to .NET 4.5, and encountered a parser issue when loading pages with an iFrame element. We have corrected this by converting of the iFrame from HtmlGenericControl to HtmlIframe. This has corrected all of the parser errors when we run our code locally.
When we deploy the app, we get the following error message:
Parser Error Message: The base class includes the field ‘frame’, but its type (System.Web.UI.HtmlControls.HtmlIframe) is not compatible with the type of control (System.Web.UI.HtmlControls.HtmlGenericControl).**
When I deploy the old code with the HtmlGenericControl the error goes away suggesting that even though we have installed .NET 4.5, the server is still using an older version?
I’ve tried removing and reinstalling .NET it making sure to register asp with IIS.
Windows 2008 R2 with IIS 7.5 and .NET 4.5
Answers:
Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.
Method 1
The basic problem is an incompatibility between the object generated from your Web Forms IFRAME server control by the ASP.NET compiler (which compiles ASPX and ASCX files to C# or VB code) and the type of the variable corresponding to that control in your Web Forms code behind. An IFRAME server control (<iframe id="frame" runat="server" />) will be parsed as a control of a particular type. In ASP.NET 4 an IFRAME server control will be an HtmlGenericControl control. In ASP.NET 4.5 an IFRAME server control will be an HtmlIframe control.
The problem can be fixed by making sure that the targetFramework attribute on the compilation element in your web.config file agrees with the Target Framework property of your project and that the variable corresponding to your IFRAME server control matches the type of control the ASP.NET compiler will generate.
An ASP.NET 4 project that has been converted to .NET Framework 4.5 in Visual Studio 2013 will modify the project’s web.config file so that targetFramework attribute of the compilation element has a value of “4.5” (<compilation targetFramework="4.5"/>). This causes the ASP.NET compiler to treat the IFRAME server control as a HtmlIframe control. This can cause a problem if the Web Forms code behind control variable is still an HtmlGenericControl. The error you see is like this:
The base class includes the field ‘frame’, but its type (System.Web.UI.HtmlControls.HtmlGenericControl) is not compatible with the type of control (System.Web.UI.HtmlControls.HtmlIframe).
The solution to the previous error is to update the type of the server control variable that corresponds to the IFRAME server control. You can do this by re-saving the Web Forms HTML file which will cause the designer file to be regenerated. As far as I can see (in Visual Studio 2013 at least) changing the control ID is not necessary. If the server control variable is in the code behind file, it must be updated manually.
An ASP.NET 4.5 project where the code behind variable is an HtmlIframe will experience a similar but different issue if the targetFramework attribute of the compilation element in the web.config file has a value of “4.0” (<compilation targetFramework="4.0"/>). This causes the ASP.NET compiler to treat the IFRAME server control as a HtmlGenericControl control. The error you see is like this:
The base class includes the field ‘frame’, but its type (System.Web.UI.HtmlControls.HtmlIframe) is not compatible with the type of control (System.Web.UI.HtmlControls.HtmlGenericControl).
The way to fix the previous error is to make sure the web.config compilation settings agree with your project’s Target Framework attribute. In this case the targetFramework attribute of the compilation element in the web.config should have a value of “4.5”.
<compilation targetFramework="4.5"/>
Note: Setting the httpRuntime element’s targetFramework attribute to 4.5 will also have the effect of setting the compilation element’s targetFramework attribute to 4.5. See https://devblogs.microsoft.com/dotnet/all-about-httpruntime-targetframework/ for more info.
Note 2: There is no <asp:HtmlIframe> tag. Registering the tag prefix “asp” to the System.Web.UI.HtmlControls namespace is not something that is required to use an IFRAME server control.
Method 2
You need to add the following tag:
<asp:HtmlIframe>
and in the designer, change the control type to:
System.Web.UI.HtmlControls.HtmlIframe
Add the following in the Web.config:
<controls> <add tagPrefix="asp" namespace="System.Web.UI.HtmlControls" assembly="System.Web"/> </controls>
This should fix it.
Method 3
We were able to fix the issue converting the
<iframe id="iframe" runat="server" />
to
<asp:HtmlIframe id="iframe" runat="server" />
Method 4
Check that you have next settings in your config file. Also make sure that it’s there after publishing.
<system.web>
<httpRuntime targetFramework="4.5" />
<compilation debug="true" targetFramework="4.5"/>
...
</system.web>
Hope it’s should help.
Method 5
You can keep your HTML element as <iframe>, and simply modify your .designer file to change the type to
System.Web.UI.HtmlControls.HtmlIframe
Method 6
Further (or in as a combination of the answers here).
I don’t believe it’s needed to actually change the tags from iframe to asp:HtmlIFrame if you have the reference to the updated System.Web.UI.HtmlControls.
I updated my web.config to remove specific versions of the tag prefix and replace it with:
<add tagPrefix="asp" namespace="System.Web.UI.HtmlControls" assembly="System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
Clean and rebuild the project and that regenerates all the designer tags for me with the correct HtmlIFrame output.
Method 7
i had also face this issue but simply i deleted this UserControl ans added new userControl with same name then my issue were fixed…..
<iframe id="logPanel" runat="server" scrolling="auto" src="">
Method 8
Look into designer file, and replace Htmliframe for HtmlGenericControl in the control that has problems.
Method 9
From .NET 4.5, Microsoft decided to change the iframe from a HtmlGenericControl to its own control, a HtmlIframe.
so you have to change the
System.Web.UI.HtmlControls.HtmlGenericControls to System.Web.UI.HtmlControls.HtmlIframe
Method 10
My solution was to just rename the IFrame and rebuild and the designer file will be updated accordingly with the correct references.
All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0