Last post Nov 29, 2006 02:30 PM by wunderkinder
Oct 16, 2006 10:00 PM|cime63|LINK
Oct 19, 2006 11:10 AM|webber123456|LINK
many have used this as a baase for development
I believe Dot Net Nuke was created from a version of this kit...
Nov 29, 2006 02:30 PM|wunderkinder|LINK
The original IBS didn't really flesh out the multiple portals stuff, even though you could add multiple entries into the Portals table. For this reason, it's easiest to think of a Portal as a single website. The portal can have an unlimited number of tabs,
and modules (*.ascx user controls) can be added to each tab. Users are added to roles, and "read" security is set on a per tab basis. "Edit" permissions are defined for each instance of a module.
So, your portal might have 2 tabs, one for each sales group in your company (aside from the Admin tab - never delete the Admin tab). Tab1 and Tab2 might each have an instance of the HTML Module. On Tab1, you can allow those in the the role "SalesGroup1"
to edit the content, and Tab2 could allow those in the role "SalesGroup2" to edit content.
As for the IBS spinoffs, they are fine if you don't mind using all third-party controls and if you don't mind having a lot of dlls and code that you don't need or use. I have been using the IBS portal for years, and I keep adding new functionality and security
to my "base" portal with each new project.