I am learning about deploying custom solutions in VS. The vid course I am taking tells me all about how to do this, but it doesn't really go into why and when one would do this as opposed to just creating solutions in SharePoint Designer.
For example, aside from a situation where a list has to do something custom that cannot be done in the browser or SharePoint Designer, why would someone create a custom list instance in VS via wsp? Also, why would they create a list definition in VS if this can be done in the browser or SP Designer?
For example, the course says that reverse engineering is the way to go rather than write a whole bunch of CAML to create a custom list. So it creates the custom list in the browser, and then imports that list into a VS solution package for either site scope or web scope deployment.
Perhaps a few real world examples of situations where this would be the way to go would be very helpful for me.
It seems like the only benefit in the case of a list instance would be that this list could be activated anywhere on the site. In the case of a list definition, i don't even really see the benefit as this can be created in the browser or SP Designer.
Thanks in advance.