| Maryann's profileItems in a sandboxPhotosBlogLists |  Tools  Help |
Items in a sandboxYo ppl, welcome to my space... Just a sandbox wit d stuff i like :) |
|||||||||||||||||||||||||||||||||||||
|
October 09 Getting started with SharePoint Object ModelIf you are working on the SharePoint Object model, look through this msdn link which explains the architecture of the object model.
For those who are familiar with the sharepoint blocks, the images below give an overview of the architecture.
Windows SharePoint Services server architecture
In the above diagram, in point 8, each SPSite site collection has an architecture as shown below:
Using Workflow Info in Custom ActivityHey folks,
Found this really good link that shows how to get useful information such as the workflow which is executing now, the list on which the workflow is attached, its history list, the item on which this workflow was triggered, etc.
The table below was taken from Phil Allen's article.
You can get the workflow details from the SPWorkflowActivationProperties object.
SPWorkflow currentWorkflow = __ActivationProperties.Workflow;
SPWorkflow exposed the following members: http://msdn2.microsoft.com/en-us/library/microsoft.sharepoint.workflow.spworkflow_members.aspx
October 01 En Garde!Found these links on script exploits that can be made in webpages.
Quoting from the 1st link:
"The primary defense against scripting exploits is to never trust information coming from a user. Assume that any data posted to your application from a browser can contain malicious script.
Similarly, any time that you write a string into a page, you should assume that the string could contain malicious script (unless you programmatically created the string yourself)." Basic Security Practices For Web Applications http://msdn2.microsoft.com/en-us/library/zdh19h94(VS.80).aspx August 13 Me Simpsonized!Have you ever wondered what I would look like as a character on The Simpsons? Never? Not even once?
D'oh! Well, anyway, I would look like this:
You can get yourself sympsonized at http://simpsonizeme.com/ April 30 Debugging custom workflows in Sharepoint 2007To debug a workflow in Visual Studio .Net 2007, you have to attach the debugger to the w3wp.exe process. However, when there has been workflow activity in this process before attaching the debugger to it, the Visual Studio IDE crashes and closes.
One way to get this working without Visual Studio IDE crashing is:
1. Reset IIS
2. Navigate to a SharePoint site (refresh the page so that w3wp process is initiated again)
3. Attach the debugger
4. Start the workflow.
|
|
|||||||||||||||||||||||||||||||||||
Send a private message
Subscribe to RSS feed
Tell a friend
Add to My MSN
Add to your network
Sign up for alerts
.gif)
.gif)
|
|
