Structural Navigation vs Managed Navigation in SharePoint

Hi Friends,

In this post we are going to learn about the navigation options present in SharePoint Online.

Below are the two main out of the box navigation options in SharePoint
1) Structured Navigation
2) Managed Navigation

What is Structured Navigation?
This is SharePoint out of the box navigation used by default and it is based on the site structure we define for our portal.

Below are some of the advantages and disadvantages using Structured Navigation.

PROS	CONS
Navigation will be updated automatically whenever Sites are added. Easy to configure. Pages are automatically added. Security trimmed, so if a user doesn’t have access to a link it will not appear in the top navigation.	Slower performance with complex navigation structure having more than 10 levels. URLs are not friendly and can be hard to memorize. Homepages belonging to structured navigation links do not appear in search when you type a search term. Cannot tag a structured navigation link to a document that it may relate to.

What is a Managed Metadata Navigation?

Managed Metadata is a hierarchical collection of centrally managed terms that we can define, and then use as attributes. It uses a dedicated term set for site navigation and the terms correspond to the friendly URL segment created.

Below are some of the advantages and disadvantages using Managed Navigation

PROS	CONS
Easy to maintain. Significantly faster page loads. Pages with term show up in search results. Documents tagged with navigation term show up in search results along with homepage of term. Friendly URLs that are easy to remember. Easy to maintain with more options to target search. Pages are automatically added.	Not security trimmed, so if a user doesn’t have access to a link in the top navigation they will still see it but can’t get to it. Sites are not automatically added. Cannot be used across site collections.

Hope this helps...

What is the difference between Local Storage and Cookies

Hi Friends,

In this post we are going to talk about when to use Local storage and Cookies.

To begin with, this is an extremely broad scope question, and a lot of pros/cons will be contextual to the situation.

Please find the below differences.

Local Storage	Cookies
Good to store large amount of data, up to 4MB	Good for small amount of data. Cookies give you a limit of 4096 bytes (4095, actually) per cookie
Local Storage allow you to store JavaScript primitives but not Objects or Arrays (it is possible to JSON serialize them to store them using the APIs)	Cookies only allow you to store strings
Local storage data is not sent to the server on every request (HTTP header) as it is purely at the client side	All data is transferred to and from server, so bandwidth is consumed on every request
It stores data with no expiration date, and gets cleared only through JavaScript, or clearing the Browser Cache / Locally Stored Data	Can specify timeout period so that cookies data are removed from browser
Local storage stores the data in the form of key and value
Not supported by anything before: IE 8, Firefox 3.5, Safari 4, Chrome 4, Opera 10.5, iOS 2.0, Android 2.0 local storage can only be read client-side

Hope this helps...

Differences Between Sandboxed and Farm Solutions

Hi Guys,
In this post we are going to list out the differences between Sandboxed and Farm based Solutions.

Farm based Solutions:
Farm solutions are hosted in the IIS worker process (W3WP.exe).It runs the code that can affect the whole farm.So whenever you deploy a farm solution you must restart the application pool or ISS Server.
If you deploy any feature or retract any feature the whole application pool got recycled.
W3WP is the worker process to which you should attach while debugging Farm based solutions.

Sandboxed Solutions:
Sandboxed solutions are hosted in the SharePoint user code solution worker process (SPUCWorkerProcess.exe).It runs the code that can only affect the site collection of the solution.
Whenever you deploy a sandbox solution, no need of restarting neither the IIS application pool nor the IIS server as sandboxed solutions do not run in the IIS worker process.
SPUCWorkerProcess is the worker process to which you should attach while debugging sandbox solutions.

Points to be noted:
•One major difference is we can't create Aplication pages in Sandbox solutions.Beacuse Application pages are stored in the 14\TEMPLATES\_LAYOUTS and when we deploy as sandbox we dont have permissions to the physical folder.
•Also we cant create VISUAL web parts in Sandbox soultions.
•We cant use code to connect to the external web services or to database in the sandbox soltion
•Farm solutions are installed and deployed. Sandboxed solutions are uploaded and activated.
• runwithelevatedprivileges doesn't work in Sandboxed solutions.
• Site collection adminstrator can deploy a Sandboxed solutions, where as Farm administrator can only deploy Farm based Solutions.

Hope this helps...