Creating InfoPath association (or instantiation) form for SharePoint 2010 Visual Studio workflow

by Kai 7. March 2012 12:07

Hi all! I’ve started exploring workflows and want to show how to create an InfoPath association form (and this tutorial also can be used to create an instantiation form, because it’s very similar process) for SharePoint 2010 Visual Studio workflow. This task is not very straight forward, and with its caveats. I’ll try to write detailed as possible guide and explain all possible pitfalls when creating form and link it with visual studio. Ok, lets start.

1. Creating and setting up an InfoPath 2010 form.

I’m going to create a very basic form, just to demonstrate how it works, but this can be a starting point for you. Run InfoPath Designer, click new, select blank form  and then design form, your empty form should look like this one:

image

Next insert a table, add a label, a texbox and two buttons. First button is Ok button, and the second is the Cancel:

More...

Tags: , , ,

InfoPath | SharePoint 2010 | Visual Studio | Workflow

How to upgrade feature in SharePoint 2010 using Visual Studio

by Kai 2. May 2011 21:36

Hi2all!

Please, refer to my revisited post, it contains more solid and working example of upgrading features using visual studio.

Today I'm going to explain how to use new SharePoint 2010 enhancement - feature upgrade. I'll create small example just to show how it works. First of all let's create new Visual Studio project and add new feature named "SomeFeature". Our feature will be install new list instance to site - Tasks list. In feature settings specify version of your feature, it must be set to "1.0.0.0". Deploy you project and make sure that your feature successfully install and new list appear. Its time to upgrade now. There is no command "Upgrade" in Visual Studio, that why we'll create own command using nice CKSDEV plugin. Go to the project settings and create new deployment configuration "UpagradeFeatures". There are three steps in configuration - Recycle IIS Application pool and two steps named "Run PowerShellScrips" from CKSDEV extension.

First script will be update our solution (.wsp file) in configuration database, the second one will find all features that need to be upgraded and call method "Upgrade" on each. Upgrade will be fire only on those features, that have version number is less than appropriate number in configuration database. SPWebApplication class has a method QueryFeatures that returns all features in web application that need to be upgraded.
Here is a code in file UpdateSolution.ps1:

param([string]$solutionPackageName, [string]$solutionPackagePath)
Add-PSSnapin Microsoft.SharePoint.Powershell -EA SilentlyContinue

$solution = Get-SPSolution | where-object {$_.Name -eq $solutionPackageName}
if ($solution -ne $null) {
  if($solution.Deployed -eq $true){
    Write-Host "Updating old version of solution package"
    Update-SPSolution -Identity $solutionPackageName -LiteralPath $solutionPackagePath -Local -GACDeployment
    Write-Host "Solution has been updated"
  }
  else {
    Write-Host "Solution package cannot be updated because it is not currently deployed"  
  }
}

More...

Tags: , , , ,

PowerShell | SharePoint | SharePoint 2010 | Visual Studio

How to extend deployment of sharepoint solution in Visual Studio using "Run PowerShell script" deployment step.

by Kai 29. April 2011 07:05

Hi2all! Today I'm going to explain how you can easily extend your deployment tasks using Visual Studio and plugin CKSDEV for Visual Studio 2010. This plugin enhance VS with many custom SharePoint project items (SPI), add additional deployment configuration for your project and some other useful details. One of the most great possibilities that CKSDEV offer are additional deployment steps:

Imagine that after deployment you must create on the site several sharepoint groups and assign permission to them. Using deployment step "Run PowerShell Script" you can place all logic reside to group creation to your custom powershell script file and execute this script file after deployment. We start with creation of script file and then we integrate script in Visual Studio 2010.
I've been created xml file definition for groups that have such structure:



    
		
            DOMAIN\FirstName_SecondName
          
	

Now lets create two files - in the first we are storing all functions and the second will use functions from this file. Call the first file "functions.ps1" and the second - "starter.ps1". "functions.ps1" include function "AddGroups" that actually read xml with group definition and adds required groups to a site. I will explain in other post how my code work, but it rather simple, if you have base knowledges of powershell you easily understand it:

More...

Tags: , , , ,

PowerShell | SharePoint | SharePoint 2010 | Visual Studio