Hi All Developers
I would like to get a best practice discussion going on the subject of developing for SharePoint because just started at a company where there are many WebApplications made - and all having their own ContentDB
All the developers (my guess they are not SharePoint Trained) insist on, that in order for them to do any kind of development/c# programming in SharePoint - they need a copy of all the Content Databases from each WebApplication in Production - whether its
C#, Stylesheets or javascript - whatever..
the argument is they get the content types, Document library, Announcement list and any customizations made etc. etc.
I disagree on this approach - if they have a Dev environment with SP installed and all the Solutions deployed they are "home free" to do whatever development there might be scoped - and they have to create the same columns if necessary etc..that way
also all solutions "starts" in dev..;-)
The current "approach" is keeping the DBA quite busy, it's taking up unnecessary space because the amount of data is enormous that needs to be moved
- but how are you expert developers handling this? - is this the "right" way of "doing" SharePoint development?
Are there any resources, drawings, process description images etc. that can show them the right way?
Hopeful they get enlightened and see: "This is how SP development is done!