I saw a call stack today from an attempt to use VSeWSS 1.3 on a SharePoint 2007 farm installation. VSeWSS is the Visual Studio 2008 extensions for Windows SharePoint Services 3.0. It requires WSS 3.0 or MOSS 2007 and also Visual Studio 2008. The SharePoint installation needs to be standalone and not part of a farm. If you install on a machine that is part of a farm here is a likely call stack from an exception during deployment of a simple web part.
[DATE] [TIME] Error System.InvalidOperationException: Feature 'XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX' is not installed in this farm, and can not be added to this scope. at Microsoft.SharePoint.Tools.Reflection.ReflectionUtility.InvokeMethod(MethodBase method, Object instance, Object parameters) at Microsoft.SharePoint.Tools.Reflection.ReflectionUtility.InvokeMethod(Type type, String methodName, Object instance, Object parameters) at Microsoft.SharePoint.Tools.SharePointProxies.SPProxy.InvokeMethod(String name, Object parameters) at Microsoft.SharePoint.Tools.SharePointProxies.SPFeatureCollectionProxy.Add(Guid id) at Microsoft.SharePoint.Tools.SharePointProxies.SPSiteFacade.AddFeature(String url, Guid id) at VSeWSS.Server.Services.SPService.AddSiteFeature(String url, Guid id)
Are you sure about it not working on a farm? I never use the standalone install option and VSeWss 1.3 works on every environment I've tried. It's possibly a masked SQL Server permission error.