I think VseWss has long way to go it is not ready to be used because it should first follow the architecture of SharePoint to be good deployment too for example :
you can create list definition using the template provided for that list definition you can create list instance in SharePoint when you create list this later reference
its list template using feature ID the problem is that vsewss change the feature ID all the time what happens is that when you uninstall solution and deploy the wsp if you had list this later will complain that it could not found the list template feature
actually this list is referring to the old feature ID the same feature had been deployed with new feature ID.
Another drawback that I think is in the fixing phase is the impossibility of using feature properties such as ActivateOnDefault, scope, etc. Because the feature files
is overwritten dynamically every time you deploy.
View Complete Post