Before we add our custom webpart to the site we need to deploy the assembly of custom webpart to the BIN directory of Sharepoint site( in which we are going to use this webpart) or GAC.
What is the difference in Deploying the Assembly to GAC or BIN of the site directory?
To GAC (Global Assembly Cache):
Advantages:-
1.If we place our signed dll in GAC it will get full trusted levels by default.
2.And also it get deployed globally so that it can be used in many applications.
Disadvantages:-
1.No site level security(Not to particular site).
2.If any changes made to assembly or rebuilt the assembly we need to force WSS to reload the assembly by restarting the ISS.
To BIN Directory:
Advantages:-
1. If we place the assembly in BIN directory , it is specific to that particular webapplication only.
2. By default this assembly run with partials security and low level CAS (Code Access Security)
3. Administrator can set the required CAS permission levels.For more information : see
Securing Web Parts in Windows SharePoint Services
Disadvantages:-
1.In order to use the assembly across multiple sites this way will not work .We need to place the assembly in GAC.
Nov 19, 2009
Basics about WorkFlows
This post provides an overview of creating Workflows using Sharepoint Portal, Managing security levels in Sharepoint Portal site.
What is WorkFlow:
A workflow is a natural way to organize and run a set of work units, or activities, to form an executable representation of a work process. This process can control almost any aspect of an item in Windows SharePoint Services, including the life cycle of that item.
You can create workflows that are as simple or complex as your business processes require. You can create workflows that the user initiates, or workflows that Windows SharePoint Services automatically initiates based on some event, such as when an item is created or changed.
Suppose you need to create a simple workflow that routes a document to a series of users for approval or comments. This workflow would include actions that the system needs to perform, as well as provide interfaces for the users to interact with the workflow in prescribed ways.
For example, send an e-mail message to the selected users when the document was ready for review. Those users would then need to be able to notify Windows SharePoint Services when they had completed their reviews and, optionally, enter any comments. The workflow framework included in SharePoint Server 2007, enables you to model such complex work processes and present them to end users in an easily understood, unobtrusive manner that guides them through each step of the process.
Workflow Types:
Windows Workflow Foundation supports two fundamental workflow styles:
Sequential workflows :Represents a workflow as a procession of steps that execute in order until the last activity completes. However, sequential workflows are not purely sequential in their execution. Because they can receive external events and include parallel logic flows, the exact order of activity execution can vary.
State machine workflows :Represents a set of states, transitions, and actions. One state is denoted as the start state, and then, based on an event, a transition can be made to another state. The state machine can have a final state that determines the end of the workflow.
What is WorkFlow:
A workflow is a natural way to organize and run a set of work units, or activities, to form an executable representation of a work process. This process can control almost any aspect of an item in Windows SharePoint Services, including the life cycle of that item.
You can create workflows that are as simple or complex as your business processes require. You can create workflows that the user initiates, or workflows that Windows SharePoint Services automatically initiates based on some event, such as when an item is created or changed.
Suppose you need to create a simple workflow that routes a document to a series of users for approval or comments. This workflow would include actions that the system needs to perform, as well as provide interfaces for the users to interact with the workflow in prescribed ways.
For example, send an e-mail message to the selected users when the document was ready for review. Those users would then need to be able to notify Windows SharePoint Services when they had completed their reviews and, optionally, enter any comments. The workflow framework included in SharePoint Server 2007, enables you to model such complex work processes and present them to end users in an easily understood, unobtrusive manner that guides them through each step of the process.
Workflow Types:
Windows Workflow Foundation supports two fundamental workflow styles:
Sequential workflows :Represents a workflow as a procession of steps that execute in order until the last activity completes. However, sequential workflows are not purely sequential in their execution. Because they can receive external events and include parallel logic flows, the exact order of activity execution can vary.
State machine workflows :Represents a set of states, transitions, and actions. One state is denoted as the start state, and then, based on an event, a transition can be made to another state. The state machine can have a final state that determines the end of the workflow.
Nov 6, 2009
Subscribe to:
Posts (Atom)