Hi there,
Another question re: infragistics. The controls on my form specifically the ultrawebgrid cause a validation error in the VS 2005 designer, which prevents me from using the design view in VS 2005.
I know the designer is not much use, but it's helpful if I want to add onclick events to buttons etc. so I really need to get this working. I apologise if the explanation is there in your helpfiles somewhere.
Thanks,
Andy
Hello Andy,
Yes, VS2005 & 2008 have this feature - treat validation warnings as errors and even prevent compilation of the project if there are validation problems (depending on the setting for Section 508, Accessibility, WCAG level 1/2/3, XHTML 1.0 / 1.1 Strict / Transitional, etc).
I can recommend switching this feature off as suggested in this blog post - this should help you continue with the project
http://weblogs.asp.net/scottgu/archive/2005/11/23/431350.aspx
As for the speciifc validation warnings autoproduced by grid in certain situations - could you please send a screenshot or more information on how to reproduce that (you can attach file by clicking reply, then finding the "Options" tab above the editing area and uploading from there - I know - not much intuitive and hard to use) - this will certainly provide additional clues and I could probably advise further.
Hi,
Thanks for your time Rumen.
I've seen Scott's blog on this and it's really very helpful. However I really wanted to prevent my infragistics controls from throwing validation errors, preventing me designing my pages whilst maintaining the validation feature. I fully understand why validation was implemented, it's not great, but a big step in the right direction IMO.
I wonder could this be because the controls have been upgraded from a previous version (5.2 - 6.? - 7.2 (current) I think)?
I've attatched a screenshot of the problem. I found the file attatch this time, don't know how I missed it!
Thanks for the follow-up and glad I was able to help. I also have found that the built-in validation does not always work the way it is expected and this is why I have it off always, but now that I see you have it with good results, I may turn it on again and see if this will increase my productivity.
Thanks again.
Ramen,
That seems to have solved the problem.
I had a script element without the type set so it wasn't passing validation at least I know now!
Thanks for replying. Indeed, I agree, validation is a good option and ir is a good idea for it to remain on, however seeing your screenshot, it really is weird to me why the ASPX page considers the UltraWebGrid ASPX declaration part of the HTML page. This should be skipped by the validation checking, since this is just the server-side declaration (various collections and properties of the grid), not the real HTML.
My guess is that somewhere on the page something breaks the validation logic (e.g. missing runat=server attribute somewhere, or some tags not being closed). If you attached the ASPX as well (zipped is better I guess), I will probably be able to reproduce this locally and see what is going on.