Tried both of the suggestons and now I get this; 

Infragistics.WebUI.UltraWebGrid.BandsCollection must have items of type 'Infragistics.WebUI.UltraWebGrid.UltraGridBand'. 'igtbl.ultragridband' is of type 'System.Web.UI.HtmlControls.HtmlGenericControl'. 

Infragistics.WebUI.UltraWebGrid.BandsCollection must have items of type 'Infragistics.WebUI.UltraWebGrid.UltraGridBand'. 'addnewrow' is of type 'System.Web.UI.HtmlControls.HtmlGenericControl'. 

Literal content ('</addnewrow>  </igtbl.ultragridband>') is not allowed within a 'Infragistics.WebUI.UltraWebGrid.BandsCollection'. 

The wierd (or annoying part) is that the "<infragistics.webui.ultrawebgrid.ultragridband " is put in there by default when you drag the control onto the page.  Is there something I'm missing but shouldn't the control handle that automatically?

I've setup the web.config as per the installtion instructions. Yet regardless of whether or not I register the assembly within the page it still appears that it does not "know" where the assembly is.  I'm thinking this because if I type "<igtbl:" intellisense doesn't find anything for it.  I've referenced it. Any ideas?

Also one other strange thing I noticed from the sintallation instructions. The assembly entry in the web.config is;

<add assembly="Infragistics35.WebUI.UltraWebGrid.v8.2, Version=8.2.20082.1000, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb"/>

But it also has a runtime binding entry of;

<assemblyIdentity name="Infragistics2.WebUI.UltraWebGrid.v7.1"

<bindingRedirect oldVersion="7.1.20071.1-7.1.20071.31"

Thanks again for the suggestions, while they didn't fix it completely it does look like they got me closer.

This problem sometimes happens when the design time assembly of any Infragistics product is not referenced from GAC. This may be related to the binding redirect sections you have for mapping 7.1 versions... I am not sure. Maybe you need to map the design time assembly as well.

Please, make sure the design time assembly for the 8.2 version of the grid is in GAC (c:\windows\assembly) and not in the /bin folder of the website you are working on, this should probabably address the issue.

 <quote>

I think you will not be able to work with the controls at design-time while the control assemblies are in your "bin" folder.  We have always accepted the fact that this breaks various things in Visual Studio, especially serialization. 

I think the main cause for this is Visual Studio loading the assembly out of your GAC in addition to the one from your bin folder, resulting in confusion about which classes come from which assembly.

</quote> 

Thanks all. 

Re: the ":" instead of "." - Thanks, simple "doh" on my part.

I still have to go in and change what the control creates when I drop it on a form - Not fun.  Removing the runtime bindings didn't help.

The assemblys are not in the BIN folder.

As I read the instructions by placing the proper entries in the web.config I would *not* have to place an assmebly tag in each page.  Am I incorrect in my understanding of that?

 Thanks 

Hi,

Is there a solution to this problem? I'm having the same issue in visual studio 2008, and every time I use the designer I have to go back and replace the tags manually, this is very time consuming and annoying, surely this problem can be fixed?

 Thanks,

Reeve.

reefer said:

Is there a solution to this problem?

What ya been smokin' there, reefer?  If you had read the entire thread, you should have seen that the original poster's problem was solved.

Maybe you should tell us more about your problem.  Post your markup, and somebody is certain to look at it.

 Hello Reefer,

Yes, I think for cases like that official contact to Development Suppotr is the better path. I can share my experinece with you on this one - I also get this behaviour once in a while reviewing customer projects and changing grid versions. From what I can tell, VS.NET at one point fails to tell the correct design time assembly to use (especially if it is not restarted after the upgrade) and there is a collision that causes this side effect (the "." namespace names in ASPX markup).

Maybe, if this is possible, removing the original old version of Infragistics and leaving only the current one on the machine, will hopefully address the issue. I have the feeling that multiple versions of GAC sometimes cause this when upgrading, but this has yet to be confirmed.

But yes, please do contact developer support via this link

http://devcenter.infragistics.com/Protected/SubmitSupportIssue.aspx

My problem is exactly the same as the original poster's problem.

If you refer to the thread the problem isn't solved, the poster still has to manually edit the markup generated after using the designer or dropping the control on the form, I wouldn't think having to manually edit the markup is a correct solution.

I've traced the problem to adding the infragistics control tagprefixes to the web.config so they are available in all pages without having to use the register syntax at the top of every page.  If I remove the tagprexes from the web.config and either manully put the register syntax at the top of the web form, or have the infragistics designer put the register syntax on the webform for me the control will serialize the markup correctly.

 However I don't think this is a good solution.

We do not like to register controls on each page in the solution, as there are hundreds of pages, and due to the desinger being very slow it is generally quicker to work with markup directly, however manually writing markup for grid controls is not fun so using the desinger is preferred.

I'm not certain when this problem started happening, as we have been using infragistics controls since 2004.x versions, but recently started working on new pages using grids with the 2008.2 version and this has started occuring again.

I think I will log a support request and hopefully this can be solved in a future release.