locked
MP and class naming structure RRS feed

  • Question

  • Hi Microsoft,

    I realize that MP development is farmed out to application teams but if there is a suggestion I could give to you for the future it would be to introduce some kind of central naming standard as currently there is almost no point in having an internal naming convention for our organization because every MP comes with its own completely non standard naming structure.

    I could go on forever with examples, but the best is perhaps the AD LDS MP, which uses the class "Services Instance".  so in my console when selecting and using classes I can go for "Word Automation Services Instance " (Sharepoint 2010 MP), "InfoPath Forms Services Instance" (InfoPath MP) or "Service Instance" which relates to, obviously, instances of the Active Directory Lightweight Directory Services class.

    Please take this posting with an element of humour in which it is meant, but joking aside, it does make larger deployments considerably more difficult if there is no coherent structure coming from the vendor.

    Mike 

    Monday, December 12, 2011 4:29 PM