While using the WebExplorerBar, when trying to reload the PersistenceFramework values (manager.LoadControl()) the following is shown in the Debug output:
Unsupported collection type ExplorerBarGroupCollection. Groups is skipped.
Basically properties like Group.Expanded or Group.Selected are not restored at all!
Infragistics35.Web.v11.2 -> 11.2.20112.1019 (same error seems to exist in .2025 as well)
Hello Leon,
Can you attach a simple project that reproduces this error.
This will help me in the investigation of this issue.
Sincerely,
Georgi Sashev
Developer Support Engineer
Infragistics, Inc.
http://es.infragistics.com/support
Just use the supplied sample for the Persistence framework (e.g. storing in the Session), but instead of persisting a checkbox try to persist a WebExplorerBar.
The issue is in your Infragistics.Web.UI\Framework\Persistence\PersistenceManager.cs line 404 (inside the LoadCollection() method), the WebExplorerBar.GroupCollectionBase is neither a IList nor a CollectionBase and as such it skips persisting any of those values in line 415.
Regards,
Leon
Here I am attaching a sample code. I cannot reproduce the described issue.
You can modify my sample in the way it is reproducible.
Looking forward to hear from you.
Try my attachment, it's your code with the following changes:
- changed to .NET 3.5
- changed to Infragistics35.Web.v11.2
- added some more groups to the WebExplorerBar
Steps to reproduce:
1. load the project and start it
2. expand one of the groups (i.e. Home)
3. submit the page (in this case by pressing your Save button)
4. try to reload the page (WITHOUT REPOSTING) - since the Session is still there, it should reload it and have the Home group expanded - but it's collapsed instead...
I am using the Infragistics dll with symbols and debug output, in which you can clearly see what I stated in my first message in this thread - those properties (i.e. .Expanded) is not persisted at all.
Hi Leon,
I did some tests, I will contact the development around this and I will update you.
Thanks for the sample provided.
This can be considered as a feature request. The client state of the control is not saved in the viewstate and is not post to the server that is why it is not persisted.
Also not all the controls and properties can be persisted.
Here is a link with some more details:
http://help.infragistics.com/NetAdvantage/ASPNET/2011.2/CLR4.0/?page=PersistenceFramework_About_Persistence_Framework.html
I have created a case on your behalf the case number is CAS-89023-KQ793X.
We can continue our communication through this ticket.
Sorry but the .Expanded property of a WebExplorerGroup is indeed saved in the ViewState and should be persisted - after all, that is the ONLY property that even makes sense to persist! (and not all the rest of the properties that specify Fonts and Colors!)
I hardly consider this a feature request, rather a BUG since your own collection is not being persisted by your own implementation code! This is also not specified anywhere in the link you sent (except that some Collections cannot be persisted), and in fact required me to debug your source in order to figure out why it wouldn't persist this ONE (!!) property (which is the ONLY one I want to persist!).
So either you guys fix your PersistanceFramework drawbacks (among many), or stop publishing this control as an "easy way to persist Infragistics controls"...