I’ve been studying ASP.NET MVC 4 over the last while; this is the subject of second of the 4 exams required for the SharePoint Developer MCSD, and I really need to spend some time on that.
The idea of an MVC (Model-View-Controller) framework is to separate the different concerns of your code, and that usually this allows you to design a data model, and then let your tools create a scaffolding of your site. Such things aren’t new; I implemented a Chinese Chess web site in Ruby on Rails which uses this approach in 2005. I loved the MVC approach. Continue reading “SharePoint vs (?) ASP.NET MVC”
No brain-dumps or anything here; if you want the answers, go and study. However, it’s worth knowing about the structure of the exam.
Right, so this is one of the 4 exams you’ll need for the MCSD SharePoint Applications. We decided to fling me at this one without preparation – I’m a SharePoint developer, so shouldn’t I be good at this one without lots of learning?
Continue reading “On the 70-488 – SharePoint Core Solutions Exam”
private static void RemoveMinimalDownload(ClientContext clientContext, Web web)
Guid MDSfeature = new Guid("87294C72-F260-42f3-A41B-981A2FFCE37A");
FeatureCollection features = web.Features;
I’ve already detailed how to create a new Taxonomy Field in CSOM – here’s the more generic how to create a general field on a list.:
internal static void CreateFields(ClientContext clientContext, List targetList, string xmlDef)
targetList.Fields.AddFieldAsXml(xmlDef, true, AddFieldOptions.AddFieldInternalNameHint);
And as a bonus, here’s how to set a field to be indexed in the client side object model:
internal static void SetIndex(ClientContext clientContext, List list, string fieldName)
Field f = list.Fields.GetByInternalNameOrTitle(fieldName);
f.Indexed = true;
This is an example of how to upload a file with the C# Client Side Object Model (CSOM):
internal static File UploadFile(ClientContext clientContext, Web web, string filePath, Folder folder, string fileName, string title)
string target = folder.ServerRelativeUrl + "/" + fileName;
FileCreationInformation fci = new FileCreationInformation();
fci.Overwrite = true;
fci.Url = target;
fci.Content = System.IO.File.ReadAllBytes(filePath);
File uploadedFile = folder.Files.Add(fci);
uploadedFile.ListItemAllFields["Title"] = title;
if (uploadedFile.CheckOutType != CheckOutType.None)
uploadedFile.CheckIn("Initial Upload", CheckinType.MajorCheckIn);
Note that this method also lets you set a title for the document, as well as the file name, and it checks the document in for you if required.
So, the client side application I’ve been working on has to sync a LOT of terms to the term store, and I’ve mentioned how I had problems with Managed Metadata labels and the ampersand – and how I fixed them using TaxonomyItem.NormalizeName().
Well, that was fine, but my application was slow – so I started looking at what I could do to eliminate client side object model calls (CSOM). My suspicion was that, as the function was static, it wasn’t doing anything that I couldn’t do in my application, and save a round trip to the server.
So, I opened up reflected and decompiled Microsoft.SharePoint.Taxonomy.dll. Inside I found the code for the following:
Regex _trimSpacesRegex = new Regex(@"s+", RegexOptions.Compiled | RegexOptions.IgnoreCase);
//Normalize name as Taxonomy Service does
string name = _trimSpacesRegex.Replace(termName, " ").Replace('&amp;', 'uff06').Replace('"', 'uff02').Trim();
That’s much, much faster than a round trip to the server, and I learnt that speechmarks are also converted from ASCII to Unicode too.
Document events are a perennial problem in SharePoint. This is, in part, due to the way documents are put into SharePoint:
- You upload the document into SharePoint…
- …which fires ItemAdded …
- …then you complete the metadata…
- …which fires item updated.
So, my problem was that our customer wanted an email sent when a document was first ‘added’ to SharePoint – except that by added they meant “Has been uploaded and it’s metadata completed for the first time”. While SharePoint does, technically, fire the correct events at the correct times, it’s pretty easy to see this ‘business event’ is probably more useful. Continue reading “Remote Event Receivers: Identify when a document's metadata is first completed”