its type (Infragistics.Web.UI.GridControls.WebDataGrid) is not compatible with the type of control (Infragistics.Web.UI.GridControls.WebDataGrid)

I got this error with the following control in asp.net 4.0.  Any idea how to fix it?  Thanks.

The base class includes the field ‘WebDataGrid1’, but its type (Infragistics.Web.UI.GridControls.WebDataGrid) is not compatible with the type of control (Infragistics.Web.UI.GridControls.WebDataGrid).

 

<ig:WebDataGrid ID=”WebDataGrid1″ runat=”server” Width=”100%” Font-Size=”X-Small” AutoGenerateColumns=”False” DataKeyFields=”ID” EnableDataViewState=”True” DefaultColumnWidth=”80px”>

  <Behaviors>

    <ig:Activation Enabled=”true” />

    <ig:Selection RowSelectType=”Multiple” CellClickAction=”Cell” />

    <ig:EditingCore AutoCRUD=”false”>

    <Behaviors>

       <ig:CellEditing EditCellCssClass=”Right”>

         <EditModeActions EnableF2=”true” EnableOnActive=”true” MouseClick=”Single” />

      <ColumnSettings>

         <ig:EditingColumnSetting ColumnKey=”ID” ReadOnly=”true” />

         <ig:EditingColumnSetting ColumnKey=”NumOfBranch” ReadOnly=”true” />

         <ig:EditingColumnSetting ColumnKey=”Total” ReadOnly=”true” />

      </ColumnSettings>

      </ig:CellEditing>

    </Behaviors>

    </ig:EditingCore>

    <ig:ColumnFixing ShowLeftSeparator=”true” ShowRightSeparator=”true” AutoAdjustCells=”true”>

       <PinButton HoverImageUrl=”~/images/icunpinned.GIF”            

ImageUrl=”~/images/icunpinned.GIF”

                            PressedImageUrl=”~/images/ICPINNED.GIF” />

       <UnpinButton HoverImageUrl=”~/images/ICPINNED.GIF”

                            ImageUrl=”~/images/ICPINNED.GIF”

                            PressedImageUrl=”~/images/icunpinned.GIF” />

   <ColumnFixingClientEvents FixedStateChanged=”WebDataGrid_FixedStateChanged” />

  </ig:ColumnFixing>

  </Behaviors>

  <EditorProviders>

    <ig:WebTextEditProvider ID=”WebTextEditProvider10″ />

  </EditorProviders>

</ig:WebDataGrid>

 

Hi HunterDevelopment,

I was unable to reproduce the problem with the code supplied. Can you give us a little bit more information about it. What version of NetAdvantage are you using? Is it a WebSite or WebApplication project? Is this a compilation error or a runtime error?

A sample project or a complete web page reproducing the problem would be very helpfull too. If you have concerns about posting it here you can send it to my email – ayordanov@infragistics.com.

Thanks.

Hi All,

I am also facing the same issue. I tried by uninstalling and re installing the Infragistics tools but still it is giving the same error.

Please suggest a solution for the same ASAP.

Regards,

Himanshu

Hi HunterDevelopment, Abhishek,

Could you please make sure that you have just one of the Infragistics4.Web or Infragistics35.Web assemblies defined in the assemblies section in your web.config.

A configuration like the following could be causing the problem.

<system.web>
 <compilation debug="true">
  <assemblies>
   <add assembly="Infragistics4.Web.v10.3, Version=10.3.20103.1, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb" />
   <add assembly="Infragistics35.Web.v10.3, Version=10.3.20103.1, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb" />
  </assemblies>
 </compilation>
</system.web>

And if that is the case one of the assemblies should be removed.

Hope this helps,

Hi,

I am also facing the same issue with WebDataGrid. I am using ASP.NET web application. I am doing migration work from Infragistics 2010.2 to 2012.2 version. And the framework is 3.5. Kindly help on this issue.

Thanks & Regards,

Rajasri M

This just started for me today.  My application had been in production and working perfectly for 6 months and then suddenly I got this error.  I tried reverting my code to older versions and it still showed the error.  In the end I removed all files from my application folder, and did a complete restore from the repo, and that got it working again.  I have no idea what caused it, but completely restoring the app from the repo was the only thing that worked for me.  I suspect the root of the issue may lie with Visual Studio.

Update: It happened again.  I've found that this only happens if I Publish through VS on my Production server, but not on my dev server.  It must have something to do with the configuration of some element in VS since it happens in debug through VS and in the published version.