SharePoint / Office 365 / Azure Blog

  http://mattberseth2.com/demo/

When creating columns (more commonly called fields) in SharePoint through the interface, you have to enter a name for it. This name is used throughout the lists and sites, included internally. Except when you try to change the name, it’ll only reflect on the outside. Internally the old name will be kept. This is because a field has two names: an internal name and a display name. When creating a field, you set both. When renaming it, you only change the display name. (There is actually no way to change the internal name afterwards) But why is this a concern? Well, in the object model it can become quite vague when to use the internal name and when to use the display name. Here is a short list with some common methods and the name they need. SPFieldCollection[name] : SPField name : DisplayName unexistent : exception SPFieldCollection.GetField(name) : SPField name: internalName, displayName or internalName and displayName from the current context unexistent: exception SPFieldCollectio...

A website allows you to encode, decode string. http://coderstoolbox.net/string/

  Ref: http://leeontech.wordpress.com/2009/08/27/databinding-in-nested-controls/ Databinding can get tricky in a hurry depending on the layout we have and the model we are binding to. Dan Wahlin suggests a way in this post Here is another way without any code or additional classes. DataContext is setup to be a instance of data, which has list of customers(having name and city as properties) and an array of strings for cities. we would like to display customers in datagrid and display list of Cities in ComboBox and select the appropriate city for the customer namespace SilverlightApplication2 {     public partial class MainPage : UserControl     {         public MainPage()         {             InitializeComponent();             this.DataContext = new Data();  ...

  Using the following GOOGLE application to reduce the JavaScript source size http://closure-compiler.appspot.com/home

  Adding the following line into the web.config of SharePoint Site. <deployment retail= “false” />   , to the   system.web  section.