The (quite dramatic) fix is usually to rename (or maybe deleted, though that is certainly more drastic! )#) this taxonomypicker. ascx data file to taxonomypicker. ascx. old (or something diffrent relevant) making sure that SharePoint does not automatically aim to load the data file. Perform this task within a test environment primary! Future service features or hotfixes may fix this trouble, but also it’s probably that TaxonomyPicker. ascx could possibly be automatically re-added during maintenance by some sort of SharePoint hotfix/service wrap up, so you needs to repeat this process again at a later stage if it isn’t predetermined.
ORIGINAL POST: With thanks to help Xiaofeng Wang (MVP) in the following paragraphs, the event wood error details usually are: “Load control design file /_controltemplates/TaxonomyPicker. ascx was unable: Could not heap type ‘Microsoft. SharePoint. Webpage. WebControls. TaxonomyPicker’ by assembly ‘Microsoft. SharePoint. Webpage, Version=14. 0. 0. 0, Culture=neutral, PublicKeyToken=71e9bce111e9429c’. ”
This is because a bug from the ASP. NET management file definition in SharePoint 2010.
To mend this issue:

Head over to: \Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\CONTROLTEMPLATES
Start TaxonomyPicker. ascx in a text editor (like Notepad)
Locate the subsequent line:
<%@ Control className=”TaxonomyPickerControl” Inherits=”Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker,Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” %>
Swap ‘, ’ that has a comma i. age. ‘, ’, the precise line should appear like:
<%@ Control className=”TaxonomyPickerControl” Inherits=”Microsoft.SharePoint.Portal.WebControls.TaxonomyPicker,  Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” %>
Save this file

Source:-http://gavinmckay.wordpress.com/2010/07/20/howto-fix-sharepoint-2010-event-log-error-7043-taxonomypicker-ascx/ .

Feature Activation

public override void FeatureActivated(SPFeatureReceiverProperties properties)
{
SPWeb web = properties.Feature.Parent as SPWeb;

}

Feature Deactivation (Reverse to Original Master)

public override void FeatureDeactivating(SPFeatureReceiverProperties properties)
{
SPWeb web = properties.Feature.Parent as SPWeb;
string urlCustom;

web.Update();
}

There are various occurrences that we should impersonate our SharePoint needs to server. Otherwise SharePoint uses system account or maybe context credentials to accomplish the task.

In my case i have to programmatically approve some sort of workflow task. ; however , i noticed it truly is showing modifiedby seeing that system account well, i used following code to vary the user recommendations to intended end user.

this will work:
base.DisableEventFiring();
item.update();
base.EnableEventFiring();

this will NOT work:
base.DisableEventFiring();
item.update();
item.delete();
base.EnableEventFiring();

So the moral of the story is, only do one event triggering action at a time, do not try to do 2 or more within one wrapper.

1. Hide the default form: Select the ListFormWebPart, right click and select web part properties. Go to layout and check hidden.
2. Insert your custom form: Click on an empty area so nothing is selected. Then go to Insert->Sharepoint controls->Custom List form, then select the list you are modifying and select the type of form. Now you can modify or delete any field!

Now you should have a “Common data view tasks” popup, if not, just click on the arrow to the right. You could then select “edit columns”. Now you will be able to add/remove/manage columns in SPD! Save the file when you done and your sharepoint site will be automatically updated with the new columns.

The SharePoint correct way to convert int to string is to use the function Convert.ToInt32(myString), btw Convert is also faster than Parse, so I recommend everyone to stop using Parse and use Convert instead even if it is not sharepoint.

Download SPBulkUpload

How to use:
1. Extract the zip file, this is actually a Visual Studios project with source code.
2. To start using the tool, copy the Conchango.Sharepoint.Utilities.BulkUpload.exe file from /bin/Debug folder to your C:\ root folder and rename it to something shorter like “spbulk.exe”.
3. Open up command prompt (Start->Run->cmd)
4. type: C: to go to your C:\ root
5. type: spbulk “c:\source folder” “http://webapp/site/target/document_library”
(replace the source folder and destination with your actual folder and site url)
6. Wait for the tool to finish.

2. Select the WebPartPages:ListViewWebPart control. (It is the place where rows of document are listed)

3. Right-click on it, Convert to XSLT Data View

4. Go into the code and find the line that says:

<xsl:value-of select="ddwrt:UrlBaseName(string(@LinkFilename))" />

5. Add this to the end of the line:

.<xsl:value-of select="@File_x0020_Type" />

6. Save

Caution: after editing the file with sharepoint designer, you wouldn’t be able to edit it with anything else except maybe Visual Studio