I will explain how to add a multilingual field with codebehind because this is quite tricky…
Let’s say you want to add a field ‘Client’ when a certain feature is activated. A reason for this to be in codebehind could be that this feature already existed and you’re writing an update. So you want the field to be added to exisitng lists aswell. And ofcourse for Dutch users it should read ‘Klant’.
So here is the code to show you how to add a multilingual field (sorry, for the layout wordpress is not so code friendly (or do enlighten me 😉 )):
So you are happily adding custom Fields, and/or FieldRefs to your ContentType, through Visual Studio for SharePoint and you deploy the outcome to your farm and when you want to activate your feature the following error pops up:
[ArgumentNullException: Key cannot be null.
Parameter name: key]
What do we want to achieve?
It is quite easy to customize a list and create a nice form in InfoPath through InfoPath Designer, but what are the required steps to make this into a solution package so it’s available with just a few simple clicks on any site in your SharePoint farm (namely by activating a few features)? And ofcourse it should open in the browser and populate the fields!
Should you ever get this error “Cannot remove Sharepoint Project item from feature” due to a null reference exception in Visual Studio 2012. Close the feature designer and re-open it.
Powershell is a great tool when working with SharePoint 2010!
However there is one thing to be wary of: BindingRedirects.
I wrote this guide about how to use resource files in SharePoint 2010 solutions for my company and often reread it, so I thought to translate it to English and share it with you.