Recently, we've had a fair few questions come in that all relate to mis-handling of assemblies and references. Mostly in conjunction with upgrading, but not exclusively so.

They don't really make for good questions for this site and should be closed; but we have no well-defined reason on our list of "reasons to close" that fits this scenario.

A few examples (not all of them clear-cut out of scope, but borderlining):

• Html.Glass helper not found after installing Glass Mapper v4
• http://sitecore.stackexchange.com/questions/4166/how-to-upgrade-weblog-for-sitecore-8-2
• http://sitecore.stackexchange.com/questions/4157/sitecore-8-2-weblog-issue-method-not-found-boolean-sitecore-caching-cache-con
• Could not create instance of the Sitecore.Forms.Core.Handlers.FormDataHandler Issue for WFFM
• "Cognifide.PowerShell.SitecoreIntegrations.Applications.PowerShellConsole,Cognifide.PowerShell" not found Error while opening Sitecore PowerShell

In case anyone is wondering why these should be closed at all, the reason is: These questions rarely (if ever) fit our format for What Makes a Good Question, they don't often give an option to provide a meaningful good answer other than "check your assembly references/configs/etc" and they often rely heavily on Q&A in comments before any conclusions can be reached.

And if we consider the longevity of the Q&A; "Issue with Glass Mapper/WFFM/SPE or whatever in 8.1" - well, often, there was no issue with either product or tech - just some basic mistakes or oversights on OPs part. We end up closing these after-the-fact.

• http://sitecore.stackexchange.com/questions/4093/how-do-i-get-the-sxa-multitenancy-to-work-in-sxa
• How to use the AntiForgeryToken with a custom log-in form?
• http://sitecore.stackexchange.com/questions/4101/sitecore-8-2-upgrade-to-8-2-update-1-issue

So. Should we add a custom "vote to close" reason to help with these types of questions? And if so, any suggestions on wording would be highly appreciated by this non-native English speaker ;-)