I still remember battling with different methods of creating wiki/publishing pages within an enterprise wiki site using code in SharePoint 2010. While the issues I encountered were almost frustrating at the time, the overall learning experience was great. So for developers like me who might be tasked with similar problems (and of course for my personal reference), I have put together this article to describe what works and what does not. I have tested the final code and found it to work for both a publishing site as well as a team site with the publishing feature activated.
This introductory tutorial presents an overview of building SharePoint web parts. Web parts are perhaps the most common type of development projects any new SharePoint 2010 developer will undertake. More detailed instructions on coding, deployment and adding of web parts to SharePoint 2010, will be presented in later tutorials.
Most Windows users usually lauch their browser application in order to search the internet. If your favorite search engine is not set as your home page and if perhaps you don’t use Google Chrome (which allows searching directly from the address bar), then you would need to first type-in the address of your search engine before proceeding. This could be time wasting and monotonous.
The designers of SQL for some reason did not require a keyword (like “ALL”) to protect SQL statements from accidental updates or deletes. Especially when the UPDATE or DELETE statement doesn’t contain a WHERE clause. I wonder if this was deliberate or if it was an oversight. In any case, the programmer becomes “all-powerful”. The significance of this problem will be better appreciated with an example…
The DataGridView is the control that is mostly used for displaying the contents of lists, tables etc. However, the built-in version of this control doesn’t allow for adding row numbers/count via its properties. This feature is often required because it is difficult to keep track of the records in a table with 1000 rows if row numbers are not displayed.
By default, .NET windows forms applications generally allow multiple instances of the same application to be started on the same machine. However, if two or more threads attempt to access a shared resource such as shared memory at the same time, concurrency issues may occur. And in a production environment, this might result in data inconsistency or inaccuracy.