Category: Uncategorized
Backup and restore data from production in sql server
Best is to use Excel as the export, import format.
Sometimes you need to change the design of the table(remove primary key, disable read-only, etc), to make it work.
select db, choose Tasks->export data, choose excel.
to restore, choose Tasks -> import data,
select the file and make sure the mappings are correct.
Make sharepoint datepicker’s textbox readonly
((TextBox)(drawDateDateTimeControl.Controls[0])).Attributes.Add(“readonly”, “readonly”);
Unblock ports on Firefox
http://blog.christoffer.me/post/2012-02-20-how-to-remove-firefoxs-this-address-is-restricted/#.VI3PQslpVWc
Mistake with app settings in web.config file
Make sure to put the settings under the correct appSettings section. In my case it was the <appSettings> section under <configSections>
Make sure files in projects are deployed to the 15 hive
Go to package and click “Manifest”, then modify the template
to make sure SharepointProductVersion is
equal to “15.0”
to make sure SharepointProductVersion is
equal to “15.0”
Can’t write log to event viewer
there are seperate accounts for farm, application pool, etc
make sure the application pool ID is included in the admin group so that logs can be written.
A feature with ID has already been installed in this farm
SharePoint 2013: A feature with ID has already been installed in this farm
When you try to deploy a Visual Web Part you may get the following error.
“Error occurred in deployment step ‘Add Solution’: A feature with ID 15/3e472a61-bbc9-4242-87c7-a07e8e3fab99 has already been installed in this farm. Use the force attribute to explicitly re-install the feature.”
See a sample screenshot of the error
The reason for the error
The Visual Studio deploys your project to the site specified by the Site URL property. Once you deployed a visual web part to a site, later from Visual Studio change the Site URL property to another site, next time when you try to deploy the project, you will see this error.
Resolution
The solution is clearly specified in the error message itself.
“Use the force attribute to explicitly re-install the feature.”
In order to specify the Force attribute, expand the Features node in your project and expand it.
Double click on the feature to open the feature.
Click on the Manifest to modify the XML for the feature file and then click on the Edit options.
You can edit the manifest in the Edit options editor. You can edit the file here, or use the link “Open in XML editor” link to open the link in the XML editor. With XML editor, you will get the intellisense support.
Add the AlwaysForceInstall=”TRUE” attribute to the Feature element. Once you modify the element, the modified element looks as follows.
Once you save the manifest, now try to deploy the project, you will find the project will deploy with out any error.
Datasheet view or Quick Edit function in Sharepoint 2013
If the custom list you’re trying to view in datasheet mode has grouping, the QuickEdit feature will be disabled.
Create a new view in which there are no grouping and you should be able to edit the list in datasheet mode
Beware of immutable types like DateTime and String
It turns out that DateTime.AddDays returns a new instance of DateTime instead of modifying the existing instance. This is because DateTime is immutable.