If you want to customize a NewForm for SharePoint list so, that users can add attachements in the same interface as other form fields, you should place control for adding attachments to a form. The problem is that this is not described and you really have to rewrite already half-prepared control.
Snippet to render Attachments Row in SharePoint 2010 Custom Edit Form
There's a common constraint in votes or surveys like "choose no more than 3 items". And it's not a good idead to allow user control the checked items quantity. You can easily set constraint to a quantity of checked checkbox items with JavaScript and jQuery. You can just disable unchecked checkbox items if user checked maximum quantity and enables items again in case of unchecking.
Strange behavior of console.log() I have noticed when I created a JS code for SharePoint page. My code used jQuery and SPServices library. The code used to get items from a list and render options for "select" control.
Below I post a part of my function which fills a JS array and renders options for "select" control.
Here is the snippet of how to Create Folder in Document Library programmatically using the Object Model. It can be used in console applications for loading documents or timer-jobs.
When I was developing a web service for SharePoint 2010 I had to fill in "assembly strong name" in .asmx file. Below I repost a very nice method how to get an "assembly strong name" in Visual Studio.
Once I had to add about 3 thousand users to SharePoint group. Usually when I have to add about 100 users, I use Excel function 'CONCATENATE' to add user login and ";" separator to generate a list of users. And then I manually enter them. But 3 thousand users – it's too much for manual.
The red star in SharePoint form for required fields can be written as <span> control with class "ms-formvalidation":
<span class="ms-formvalidation"> *</span>
While removing Site Content Type you got the error that "The content type "My Content Type" is part of an application feature". The fix is rather easy and simple.
Managed metadata is very good and powerful tool in SharePoint. But it has some not very comfortable specialties during migration data from one farm to another, for example, from test environment to productive. You can export your managed metadata from one site and import it into another one. But here's the problem that each termset and term has its own GUID. After you import managed data into the new farm, new GUID’s will be assigned to managed data items.
