I'm a .NET programmer and I've got thrown at me the maintenance of a couple of SharePoint 2010 and 2013 portals with very little training.
Some of the things I've been told are:
- SharePoint Designer, both the 2010 and 2013 versions, is awful and prone to data loss;
- I should always use the copy of Designer installed locally where SharePoint server is installed and never use it from my computer connecting to the SharePoint server through the network;
- I should never "save" an item - any item - but always "save as" it with a different name and change everything to point to the new version;
The reason for these statements is always "because it screws up when you save and you'll lose everything" with no explanation to back it up.
I tried looking around here but I couldn't find any decisive evidence of these problems, and as a programmer I'm not satisfied with a "it doesn't work" / "because I say so" answer, especially when I've been tasked with the maintenance.
I'd like to know if SharePoint designer really has the problems my colleague mentioned or if it's some kind of cargo cult due to missing knowledge of the products and/or problem with the infrastructure (e.g. wrong setup, corrupted database, etc.) which should be investigated further.