Learning SharePoint

Visual web parts VS Standard web parts 1. A standard web part is an item-level template in Visual Studio. That means that you can only add it as an item to your project (an empty SharePoint project for example). A visual web part can be created as both item-level and project-level. 2. In the case of the visual web part, you can use a designer experience to drag and drop items on your canvas. In the case of the standard web part, you will have to manually type everything (using IntelliSense). 3. A standard web part can be deployed as a Farm or Sandboxed solution. A visual web part will have to be deployed as a Farm solution. Web Parts vs. User Controls One of the limitations of user control is that they cannot be shared across web applications but they can be created using a designer tool. On the other hand if you take custom controls, they can be shared across web applications, but there is no visual designer for creating custom controls through which we cannot drag and drop ...

Sometimes it is the case when your SharePoint server keeps on prompting for credentials. After some amount of googling and going through some reliable blogs I found following solution. Open Run Type “regedit”.                                                                  In the registry window left panel find HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > LSA                                                                                                                      Now right clic...

Sometimes there are situations where we need to create site collections with a specific content database. You could achieve this using the below steps.   Create / User existing web application in which you want to create site collections . Go to Central Admin > click Application Management > click Manage Content Databases  Select your desired web application (the one in which you want to add site collections). You can see below screen now, Note: You will be able to see a database name that is the database with which your web application is associated. In case you create a new Site collection in this web application then by default the visible database will be used.    3. Click Add new Content Database, below screen appears          4.        Add new database name and click OK, in my case I am creatin...

A host-named site collection allows you to address a site collection with a unique DNS name, such as “ http://collection1.com ” .  Typically you will create a SharePoint web application, and it contains many path-based site collections that share the same host name (DNS name).  For example, collection1 has a site collection at “ http://mywebapp.com/sites/collection1 ” , and collection2 has a site collection at “ http:// mywebapp.com/sites/collection2 ”.  These are referred to as path-based site collections, and is the recommendation for most corporate scenarios.  Host named site collections enable you to assign a unique DNS name to site collections.  For example, you can address them as http://collection1 .com and http://collection2 .com , which enables hosters to scale to many customers. SharePoint makes the decision on how to map the host name to the site collection when the SPSite object is constructed.  It internally uses the SPWebApplication ob...

Normally when you create a web application in SharePoint its Url is: “ http://<Server Name>:Port” or “ https://<Server Name>:Port ”. We can also create a web application that contains a URL that is not of the above format, instead it could be “ http://mywebapp.sharepoint.com ” or “ https://mywebapp.sharepoint.com ”. In order to create, host named web application following steps is needed to be followed. 1.       We need to create a host name in the DNS. The host name will be the url, the site. In my case my host name will be “mywebapp” . 2.       You need to login to your Active Directory server to create new host entry in DNS. 3.       Create DNS entries 4.       Let’s go to the DNS server and create a new A Host with the   “mywebapp.sharepoint.com” FQDN and pointing to the web front end.   5.     ...