Hi there,
This is a pretty general question as I'm really only just scratching the surface on SP.
I have an existing (simple-ish) list solution/feature that has been developed as a VisualStuido 9 project for Sharepoint2010.
We have a test and prod site, we have no dev setup.
Our installations are SP2013 with "2010 mode" collection.
Users want to change this list - there are about 10 column changes, mostly renames, but some of the choice lists options are changing on a contentType
the forms in use are all just modified versions of the default forms (no infopath used I think, just webparts added with some JS code to show things and open PDF in browser or something).
There is a workflow (basically email business area on some event reciever event firing)
My questions are:
a) since we have no development enviornment - should we setup "Workstations with SP on client and visual studio" or should we build a server and install visual studio on it and remote into it for development? We are a very small team of developers. so only one person will work on this stuff at a time but this person may change quasi frequently.
b) I think we could make most of these changes by modifying the column names and choice lists in the SP interface, as opposed to learning how this development/deployment thing works with SP and setting up a DEV environment... however for migrating these we would have to document this and copy the process between environments - also I'm not sure how this would effect the event reciever (although from my breif look its relying on the "underlying" column name, so this shouldn't change)
c) the existing solution is setup as 3 separate features - why would that be a decision rather than one feature that contains all related items? (looks like one is the event reciever, one the customised list and one the content type(s) and site columns...
Given all this can anyone advise on best course of action from here?
- sure I'm noJedi but that's no reason to stop trying to make stuff levitate! -