I'm working in a user area and am limited to Sharepoint development on the client side only. This means that all custom forms and their associated scripts will live in site libraries instead of on the server. Taht's my biggest limitation. In researching the appropriate development tools, I've run into more questions than answers, and am hoping to get some real-world experience from others managing a similar situation:
1.) I've heard that given the choice between SPDesigner and Visual Studio, I should avoid Designer. However, no one can tell me why. If I know Microsoft, I would guess that the drag-n-drop nature of the interface generates some incredibly bloated code compared to creating something myself in VisStudio. Is that a correct assumption? What are some of the other (if any) pros and cons of using Designer over VisStudio? Are there instances where one is clearly desirable over the other?
2.) Assuming that I do get special dispensation from IT to orderm and run Visual Studio (and I'll ahve the choice between v10 and v11), can I do all my development pointing to the site level (of which I'm an admin) instead of at the farm level? My requirements dictate that nothing be deployed on the server. Can anything developed in VisStudio live in the doc libraries? or must it all be housed at the server level?
3.) Does VS require any sort of permissions granted, or does SP magically know what kinds of permissions to grant to VS?
4.) Where does my code eventually need to live? in the site's document library? or can I put it somewhere in my sites where it would be available to all subsites...in the same way that the site columns are accessible to any subsite? Again, though this time regarding where code is deplayed, does VisStudio have limitations that Designer doesn't and vice versa?
5.) Knowing very little about Designer and Visual Studio, can anyone recommend some good online tutorials or resources? or at the very least, an effective Google keyword or two that'll kill some of the noise I'm finding.