We have multiple applications that are separate but related.
Each application has multiple instances of controls that we would like to persist the state for in SQL.
When storing this is it just using the control ID to uniquely identify the settings for that particular control?
Essentially, do I need to worry about naming collisions across applications and store a separate record for each application?
Obviously this will inform the table schema and the implementation of the provider that are needed.
1 Answer, 1 is accepted
0
Hello ,
Generally you need set a unique StorageProviderKey for each PersistenceManager control in your application. Another possible solution is to use PersistenceManagerProxy where you can specify a UniqueKey to each instance of the control.
Regards,
Kostadin
Telerik by Progress
Generally you need set a unique StorageProviderKey for each PersistenceManager control in your application. Another possible solution is to use PersistenceManagerProxy where you can specify a UniqueKey to each instance of the control.
Regards,
Kostadin
Telerik by Progress
Check out the new UI for ASP.NET Core, the most complete UI suite for ASP.NET Core development on the market, with 60+ tried-and-tested widgets, based on Kendo UI.