I've created a Task class similar to the one found in .NET Framework v4, because I needed to handle some asynchronous tasks in some of our legacy v2-targetting software.  The class is in the Acom.Threading.Tasks namespace, Acom being our company name.Now I'm wondering what is the best way to 'house' this sort of code that is not specific to an application - what assembly should it live in, and what should the assembly be called?I envisage new classes appearing at a very low rate, maybe one per year as a guess.We've considered creating a general catch-all assembly to contain it and future code, but then comes the problem of what to call the assembly.  Names of the form Acom.Common.dll and Acom.Shared.dll could be used, but they don't really describe what the thing represents.What is best practice in this case?Please note that this question has been re-worded.  It would be nice if it could be re-opened so that I, at least, could provide the answer to help others with a similar problem in the future.
What is the best practice for 'housing' code that is not application specific?
c#;.net;naming