Today for a new menu item its create code and add it to the system. It leads to possible errors in adding menu items and a deployment of code.
For this system, it would do a recursive table lookup that can be used on the left hand side menu. Create code for a system when a table lookup can be implemented. Pardon the pun ‘one set of code; does it all’ forever.
Possible issues and problems: a) the css/style sheets in displaying the menu b) create a CRUD to a table to create a listCollection that would be separate from the existing abp.io framework; so new releases do not affect abp.io updates.
All systems could use this over coding but a eCommerce system would have the most need. If this could integrate with purchasing and security areas of abp.io framework, even better. Example: for Tenant1, I create User1 who has access to MenuItem1 due to Tenant1 purchase and / or to display product.
In a previous job we had this in a asp.net 2.0 app. it worked great. Only issue was when new items were added, a logoff was needed to see the new item.
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.Ok
Mike can you please explain your requirements a bit more??
Today for a new menu item its create code and add it to the system. It leads to possible errors in adding menu items and a deployment of code.
For this system, it would do a recursive table lookup that can be used on the left hand side menu. Create code for a system when a table lookup can be implemented. Pardon the pun ‘one set of code; does it all’ forever.
Possible issues and problems: a) the css/style sheets in displaying the menu b) create a CRUD to a table to create a listCollection that would be separate from the existing abp.io framework; so new releases do not affect abp.io updates.
All systems could use this over coding but a eCommerce system would have the most need. If this could integrate with purchasing and security areas of abp.io framework, even better. Example: for Tenant1, I create User1 who has access to MenuItem1 due to Tenant1 purchase and / or to display product.
In a previous job we had this in a asp.net 2.0 app. it worked great. Only issue was when new items were added, a logoff was needed to see the new item.