Accessing Virtual Disks Via Windows

Accessing Virtual Disks Via Windows: "Accessing Virtual Disks Via Windows

One of the often overlooked features of VMWare Workstation is the Virtual Disk Mapping utility. Available through the standard VMware Workstation GUI, the tool maps a Windows drive letter to a virtual disk used in a VM. Mapping a virtual disk can be done much quicker and easier than launching the VM to access the files on the virtual machine’s disks. This functionality ships with VMware Workstation for Windows; other tools are available for Linux users, but won’t be covered in this article.

- Sent using Google Toolbar"

3. A Quick Start Guide to TortoiseHg — TortoiseHg v1.1.3 documentation

3. A Quick Start Guide to TortoiseHg — TortoiseHg v1.1.3 documentation:

"3. A Quick Start Guide to TortoiseHg¶

Send Email to multiple users using sharepoint object model Or API

Send Email to multiple users: "you can use this method to send emails.

SPUtility.SendEmail (SPWeb, Boolean, Boolean, String, String, String)


if you need to send multiple emails you have to use a loop and within that you

have to set email addresses to the method and send mails in a loop.

examples are available in
http://www.sharepoint-amila.blogspot.com/"

Error: New instances of this workflow template are currently disallowed. - Microsoft Premier Field Engineer - SharePoint Dev - Site Home - MSDN Blogs

Error: New instances of this workflow template are currently disallowed. - Microsoft Premier Field Engineer - SharePoint Dev - Site Home - MSDN Blogs: "Sometimes we may get this error whenever we re-install the workflow after doing some changes. It may come once you un-install the workflow and install it again.Now how to allow new instances for workflow?To resolve this problem we need to set the workflow association to 'Allow' and the new instances of the workflow should be created again. In order to set this option, what we need to do that, go to the Remove Workflows settings page by List à Settings à Workflow Settings à Remove Workflows.And here we need to select the “Allow” option."

SharePoint workflow new instance's not allowed - Fix

Error: New instances of this workflow template are currently disallowed.
ex.StackTrace : at Microsoft.SharePoint.Workflow.SPWorkflowManager.StartWorkflowElev(Object context, SPWorkflowAssociation association, DateTime elevationTimeUtc, SPWorkflowEvent startEvent, SPWorkflowRunOptions runOptions) at Microsoft.SharePoint.Workflow.SPWorkflowManager.<>c__DisplayClass11.b__10(SPSite superUserSite, SPWeb superUserWeb) at Microsoft.SharePoint.SPSecurity.<>c__DisplayClassc.b__a() at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass4.b__2() at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode) at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param) at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode) at Microsoft.SharePoint.Workflow.SPWorkflowManager.StartWorkflow(Object context, SPWorkflowAssociation association, SPWorkflowEvent startEvent, SPWorkflowRunOptions runOpts) at Microsoft.SharePoint.Workflow.SPWorkflowManager.StartWorkflow(Object context, SPWorkflowAssociation association, String eventData, SPWorkflowRunOptions runOptions) at

Solution using web UI:
Got to the List worflow settings and hit the remove this workflow and select the Allow option to resolve new instance not allowed error.

Add SharePoint workflow to a list programmatically - Stack Overflow

Add SharePoint workflow to a list programmatically - Stack Overflow: "// 1. create an instance of the SPWorkflowAssociation class SPWorkflowAssociation workflowAssociation = SPWorkflowAssociation.CreateListAssociation(workflowTemplate, associationName, taskList, historyList); // 2. set start options workflowAssociation.AllowManual = true; workflowAssociation.AutoStartChange = false; workflowAssociation.AutoStartCreate = false; // 3. set additional association options (if any) workflowAssociation.AssociationData = associationData; // 4. add workflow association to the list list.WorkflowAssociations.Add(workflowAssociation); // 5. enable workflow association, so it is displayed in the user interface workflowAssociation.Enabled = true;"

Hugo's Blog > How to start the default approval workflow programmatically

Hugo's Blog > How to start the default approval workflow programmatically: "How to start the default approval workflow programmatically
Posted by: Hugo Esperanca - Tuesday, September 07, 2010
Today I was trying to find a way to programmatically create a publishing page and start the default approval workflow attached to the pages library"

SharePoint Kings: How to start workflow programmatically

SharePoint Kings: How to start workflow programmatically: "How to start workflow programmatically"

Tony Testa's World | Howto Start a Sharepoint Workflow Programmatically

Tony Testa's World | Howto Start a Sharepoint Workflow Programmatically: "Howto Start a Sharepoint Workflow Programmatically"

Unable to close the web part dynamically

Unable to close the web part dynamically: "Unable to close the web part dynamically"

Adding and Deploying Solutions with PowerShell in SharePoint 2010 - Corey Roth

Adding and Deploying Solutions with PowerShell in SharePoint 2010 - Corey Roth: "Adding and Deploying Solutions with PowerShell in SharePoint 2010"


You might want to update your solution, so we’ll talk about how to do that as well. Here is what your stsadm command might have looked like in WSS3. Which would also be followed up with an execadmsvcjobs operation.

stsadm –o upgradesolution –name SharePointProject2.wsp –filename SharePointProject2.wsp –immediate –allowCasPolicies

The upgrade solution syntax is similar to the others. We just have to specify an identity and a literalpath with the Update-SPSolution command. The identity is the name of the package on the server to upgrade and the literalpath is the full path to the new solution package on the file system. Here is what that might look like.

Update-SPSolution –Identity SharePointProject2.wsp –LiteralPath c:\code\SharePointProject2\bin\debug\SharePointProject2.wsp –GACDeployment

Content Type Deployment Error

Content Type Deployment Error: "I have the same issue. I also have site columns. It seems to me that VS 2010 complains about either the contenttype id or the site column id.
I put Jent's suggetion in, it did not work.
I also has Overwrite='TRUE' and it did not work.
Then I went to web UI and I was able to activate the feature from the web UI.
Very strange problem."

Note: I was also able to activate using the web UI really strange, I did not try either STSADM / Powershell to active this feature this may also fix the issue.

Setting a Custom Edit Form for a Content Type « SharePoint FieldNotes (Steve Curran)

Setting a Custom Edit Form for a Content Type « SharePoint FieldNotes (Steve Curran): "Setting a Custom Edit Form for a Content Type
Technorati Tags: WSS SharePoint

This post is about a quirk regarding setting a custom edit form for a content type in a document library. There was a great post by Ton Stegeman /tonstegeman/archive/2006/10/29/15374.aspx regarding creating custom edit forms for Sharepoint content types. Once you had created your edit form and deployed to the layouts directory you had to set the “EditFormUrl” property of the content type. This works great. Unfortunately, I had a requirement where the client wanted to turn this custom edit form on and off. For example, from a configuration page the customer would choose a content type associated with a document library and then check a check box to enable the custom edit form, or uncheck it to disable the custom edit form and go back to the default. I thought you could just set the “EditFormUrl” property to an empty string or null and then update the content type and the document library. However, after doing this the “EditFormUrl” property was still set to my custom edit form. When developing on SharePoint you tend to feel like Thomas Edison. You know 10,000 ways something does not work. So after much experimentation I was able to get the “EditFormUrl"

Deleting Content Types

Deleting Content Types

Note:
1) Choose the Sharepoint Console Aplicaiton (CKSDev) template rather than default VS console applcaiton.

2) Incase if you have issues check if web application has the root site if not they create one and try...as per on of dude in many instance sp2010 is using the web application's root site to get the required information. I don't have a example in mind to share here.

Choose the 32-bit or 64-bit version of Microsoft Office - SharePoint Designer - Microsoft Office

Choose the 32-bit or 64-bit version of Microsoft Office - SharePoint Designer - Microsoft Office: "Choose the 32-bit or 64-bit version of Microsoft Office
Applies to: Microsoft Access 2010, Excel 2010, InfoPath 2010, OneNote 2010, Outlook 2010, PowerPoint 2010, Project 2010, Publisher 2010, SharePoint Designer 2010, Visio 2010, Word 2010"

Note: Check out the office 2010 version on your machine if its 32-bit then you can only install 32-bit. you can't install designer 64-bit on it vice versa.

Using the undocumented SPUtility.SendEmail method. « Blog of an overweight SharePoint addict

Using the undocumented SPUtility.SendEmail method. « Blog of an overweight SharePoint addict: "Using the undocumented SPUtility.SendEmail method."