sounds like a good idea John!

Are you going to lig it into Gemini, please? Thank you!

lets wait with gemini ;)

even though we might add it back, i think its not a good idea at all, for the following reasons:

• the new paradigm in DNN 5 is that are are NO admin tabs at al anymore, the only special kind of tab is the Host tab, which can be found by checking for the IsSuperTab property of TabInfo
• Admins can now easily create their own admin like pages. By all means those pages would also have to be covered by the "IsAdminTab" attribute
• Admins can now easily change the name of the admin tab. The tabpath changes then (in fact i just found a bug there, the tabpath of the child pages are not updated accordingly...)
• You can now decide to make the admin menu visible to more roles. Will the admin menu still be an admin menu that way?
• the original poster says: "software already written expecting a 'true' will do strange things because the property no longer means anything". This is true. You should not expect your software to behave exactly the same in a new platform version. Even though your module might not break, that is no guarantee that its functionality might not change slightly. IMHO this is true for DNN as much as any other platform, like .NET and Windows. It just means you need to test your software

IMHO it is correct that the property has been marked obsolete, and it should be removed in a future version (knowing our track record for not removing obsolete functions for a very long time means that it will probably be around for quite some time). If this would be added as new issue in gemini, my vote would be to withdraw / not fix

DNN Blog | Twitter: @erikvb | LinkedIn: