In one of my previous blogs I have mentioned that there is a serious problem if you want to develop SharePoint 2007 solutions using Visual Studio 2008: SharePoint Solution Generator (SSG) doesn't work on such an environment. Personally I use SSG quite a lot while working with custom lists: I can configure the list using the SharePoint GUI and then extract its definition and incorporate it in my Solution.
Waldek is a Microsoft Office Development MVP and Head of Product at Rencore where he designs and builds market-leading solutions that help SharePoint and Office 365 customers to minimize risks from customizing SharePoint. As a member of the SharePoint PnP core team, Waldek helps SharePoint developers get the most out of SharePoint’s extensibility capabilities. For his contributions to the technical Microsoft communities as a blogger, speaker, and developer, Waldek is a 10-time recipient of the Microsoft MVP award.
SharePoint 2007 has built-in support for Resource files helping you achieve localization. Using these files you are able to set localized labels for the resources being provisioned. Furthermore you are able to use Resource files within your assemblies to support localization on run time. Yet there is something wrong with localization in SharePoint 2007...
Visual Studio 2005 extensions for Windows SharePoint Services 3.0 (VSeWSS) ship with a useful tool called SharePoint Solutions Generator. One of its features I use most often is creating a List Definition based on an existing list. Since the CAML schema of a list isn't really straight-forward - especially if the list uses complex settings and multiple custom views it's almost undoable to create such schema manually. Another possibility could be using List Templates instead of List Definitions. List Templates are unfortunately impossible/difficult to customize and should be used, in my opinion, in SharePoint configuration scenarios when there is no other choice. SharePoint Solution Generator comes very useful if you want to work with List Definitions but you don't want to type all the CAML yourself.
While working with the SharePoint Solution Generator (a utility which ships with Visual Studio 2005 extensions for Windows SharePoint Services 3.0) I have stumbled upon an interesting by-design feature which affects the way you develop Features - at least if you're using or planning to use the SharePoint Solution Generator (SPSolGen).