Just a quick question about proper helper dll dev. I want to deploy a set of classes in a helper dll for a bunch of features to use. I remember back in 2007 I had to create a class and compile, then a separate sharepoint feature to house the dll. I'm wondering if that is still the proper way of deployment or if I can simply create an empty sharepoint feature and create a helper dll in that feature and deploy.
Sorry guys for not chiming in on this, been away. I simply wanted to know what the best practice was for deploying helper style assemblies that multiple SharePoint solutions reference. Yes I can simply drop that custom assembly into the GAC manually on each server in the farm, but I wanted to know about a more automatic way of performing this task.
In SharePoint 2007 I would simply piggyback a custom assembly in one of my site wide feature solutions. Creating the “GAC” folder and let WSPBuilder do the rest. I just wanted to know if it was the same process in SharePoint 2010. If I add the custom assembly in the Package definition declaring it as a safe object for each of my SharePoint solutions that need to reference this helper dll it of course is deployed correctly with no fowl. However if I decide to deactivate and retract one of those projects with the reference it in turn removes it from the GAC orphaning the rest of the projects that have the same reference, causing everything to grind to a halt until the helper dll is reinserted into the GAC.