https://connect.microsoft.com/VisualStudio/feedback/details/553061/vs2010-copy-paste-functions-are-not-working-as-expected?wa=wsignin1.0

Since Dec, 7th the SP1 Beta is availalbe, which fixes the bug.

You can download the SP1 Beta from here: http://go.microsoft.com/fwlink/?LinkId=207130

In one of my custom display forms I wanted to add the taxonomy feature and the relevant properties from the column settings. To archieve that I did the following:

Adding a reference to the control:

<%@ Register TagPrefix="Taxonomy" Namespace="Microsoft.SharePoint.Taxonomy" Assembly="Microsoft.SharePoint.Taxonomy, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

Inserting the control:

<Taxonomy:TaxonomyWebTaggingControl ID="taxonomyCntrl" runat="server" />

In the code behind (C#) class I put the properties to the control:

public static TaxonomyField GetTaxonomyFieldOfList(string listname, string fieldname){
SPList questionList = SPContext.Current.Web.Lists[listname];
return questionList.Fields[fieldname] as TaxonomyField; }
-----------
TaxonomyField taxonomyInfo = SPListUtility.GetTaxonomyFieldOfList("list name", "Tags (=column name)");
if (taxonomyInfo != null) {
this.taxonomyCntrl.SspId.Add(taxonomyInfo.SspId);
this.taxonomyCntrl.TermSetId.Add(taxonomyInfo.TermSetId);
this.taxonomyCntrl.IsAddTerms = true;
this.taxonomyCntrl.AllowFillIn = true;
this.taxonomyCntrl.IsMulti = true;
}

This is the code to set the necessary properties for the managemend metadata.

For saving back the value to the list the following code could be used:

TaxonomyFieldValueCollection tfvc = TaxonomyFieldControl.GetTaxonomyCollection(this.taxonomyCntrl.Text);

Nintex Workflow 2010 offers functional and feature rich SharePoint workflow to your organization. It takes the powerful-yet-easy design, deployment, management, and integration features of Nintex Workflow 2007 to the SharePoint 2010 platform, with improved process monitoring, extensibility, and designer productivity.

• Any SharePoint user can create and maintain elaborate workflows using a browser-based graphical web browser interface
• Monitor and manage workflow activity across lists, sites, collections, applications, and farms
• Maximum value with minimum footprint and minimal IT administrative burden
• Extend design and runtime options using Windows Workflow Foundation expertise

Nintex published the following videos:

There are still lots of more new functionality – just have a look to the videos.

This error seemed pretty strange to me because the assembly wasn’t located on a network share but simply on my local machine. After some time of researching I found an article on the web (thanks to Winston Johnston) where the solution is described:

Am DevCamp gab es lediglich einen Vortrag von Stephan Kitzler-Walli, der sich mit komplexen Dateneingabemasken für SharePoint 2007 beschäftigte. In diesem Vortrag ging es darum, Dateneingabemasken, die ab einer bestimmten Datengröße unübersichtlich und unhandlich zu bedienen werden, übersichtlicher mittels Silverlight zu gestalten. Die neue Eingabemaske wurde für einen Inhaltstypen erstellt. Inhaltstypen bieten folgende Vorteile: Vorlage für Metadaten, Vorlage für Dokumenttypen, Wiederverwendbarkeit, Vererbung, … – daher eignet sich die Maske für eine Inhaltstyp zu erstellen sehr, da automatisch alle vorhandenen Eingabemaske mit der neuen Maske ersetzt werden.

Folgende Maske veranschaulicht eine Bearbeitungsmaske des Datentyps „Kontakt“, die aufgrund der Länge bereits sehr unübersichtlich ist.

Im Rahmen des einstündigen Vortrages, wurde live anhand eines Codebeispiels eine neue Silverlight-Eingabemaske erstellt. Diese Eingabemaske basiert auf einer XAML-Datei, die die Layout-Struktur des Formulars definiert. Die Felder werden dynamisch mittels Reflection aus dem Inhaltstypen gelesen und auch dynamisch im Silverligth-Formular angezeigt.

Die neue Eingabemaske sieht ein verbessertes Layout vor, bei dem die Eingabedaten thematisch auf mehrere Tab-Reiter verteilt werden. Bei Aktivierung des Features werden die Standard-SharePoint-Eingabemasken des Inhaltstyps „Kontakt“ durch die  Silverlight-Eingabemaske ersetzt. Egal, wo in der SiteCollection nun eine Kontakt-Eingabemaske angezeigt wird, diese wird durch die neue Maske ersetzt.

Die Präsentation, der SourceCode sowie das Video zu diesem Vortrag sind unter http://www.devcamp.at/Archive.aspx verfügbar. Leider ist da Video des Vortrages derzeit noch nicht fertig – diese stehen ab ca. Mitte November zur Verfügung.

Now I would like to explain the new Visio features more detailed. Opening Visio the first time, you will see that Visio 2010 comes with a new template – Microsoft SharePoint Workflow.

This template offers quite new shapes for SharePoint workflows, which are separated into the following groups:

• SharePoint Workflow Actions

• SharePoint Workflow Conditions

• SharePoint Workflow Terminators

I started to design my first Visio workflow, which is a simple request for leave. The shapes can be inserted quite easy – just drag and drop it to the page. After connecting the shapes my workflow seems to be finished.

Before exporting the workflow to the Visio Workflows Interchange file, you have to check the diagram. If any error occurs, it’s not possible to export the diagram.

In my case I used custom conditions twice (as you can see in the diagram). Unfortunately, check process was not successful. It seems that the check process did not recognize the custom condition shapes. Therefore the other shapes are not connected to the workflow.

I also tried to ignore the rule, but nevertheless the diagram could not be exported. I hope that this is just a bug of the Technical Preview and will be solved in the next version of Visio.

So, I will explain the generated Visio Workflows Interchange file with another example. I just created a simple diagram with two shapes.

Yehh – that validation worked. So I exported the vwi file. That file contains different files, which can be viewed by changing the extension to *.zip. The following files are created:

• [Content_Types]
  This file summarizes the used extension and their content type.

• Workflow.vdx
  is the Visio diagram in xml-format. Actually it’s not that interesting; it’s just a long file defining the Visio layout (and data) in xml.

• Workflow.xoml
  The xoml file describes the workflow itself. If you familiar with SharePoint Designer 2007 workflows you will know the structure of the file – it’s similar to that.

• Workflow.xoml.rules
  That file simply references the xml namespace.
  <RuleDefinitions xmlns=”http://schemas.microsoft.com/winfx/2006/xaml/workflow” />

Importing vwi-file to SharePoint Designer 2010

First of all, the new SharePoint Designer 2010 looks very cool and Microsoft improved a lot of things. It’s now possible to administrate the whole SharePoint site with that designer. You can configure page information, create and modify lists, document libraries, subsites, permissions, content types, workflows, … .

The following picture shows the start page when you connect to an existing SharePoint 2010 site.

Clicking on the workflow section opens the workflow tool pane, where you can edit existing workflows or add new ones.

The best innovation in my opinion is that you can now create reusable workflows with the designer. This was not possible with the previous version of SharePoint (Designer). In 2007 you had to create reusable workflows with Visual Studio.

The easiest way to continue with you Visio workflow is just to import it from Visio by clicking the button in the ribbon menu. The import wizard offers you the possibility either to import the workflow for lists or to create a reusable workflow.

As you can see in the next image, the Designer creates the structure of the workflow. You can now go on with adding the logic to the workflow. The actions are similar to the actions in SharePoint Designer 2007.

You can start editing the actions, add new steps and actions and at the end publish the workflow to your SharePoint environment.

Before exporting the workflow to SharePoint it’s recommended to check for errors. If any error occurs the position is highlighted.

<Query>
  <Where>
    <Eq>
      <FieldRef Name="hsg_ApproverList"></FieldRef>
      <Value Type="User">$Resources:hsg_Resources,Me;</Value>
    </Eq>
  </Where>
  <OrderBy>
    <FieldRef Name="FileLeafRef"/>
  </OrderBy>
</Query>

In my code I tried to replae the resource string with the correct phrase – like [Me]. Reading the data from the resource file works as expected.  After deploying the list to sharepoint and create a new instance of the library, the view  is not working. There are no entries shown in the view. When looking to the view settings everything looks fine ([Me] is showed as filter value).
After pressing the OK button, the view is working correct.

This leads me to the opinion that my filter value is wrong and is replaced by a woking one (when pressing the OK button). But how should I find out the correct value? So I did a trick:

• Save the list (with working views) as template (*.stp) file to sharepoint
• Download the *.stp file
• Rename the *.stp file to *.cab file
• Open the *.cab file -> extract the manifest.xml file
• Look for your custom filter query
• And yehhh -> you get the correct filter value

The correct filter value now looks like the following example:

<Query>
  <Where>
    <Eq>
      <FieldRef Name="hsg_ApproverList"></FieldRef>
      <Value Type="Integer">
        <UserID/>
      </Value>
    </Eq>
  </Where>
  <OrderBy>
    <FieldRef Name="FileLeafRef"/>
  </OrderBy>
</Query>

<UserID /> is the solution – the view works fine now. The view settings in SharePoint UI look like before.

Filter in view settings

SetValue() is the right choice, but DateTime.Now.ToString() fails, because the XML format is not correct. After some researching I found out, that DateTime.Now.ToString(“s”) is the right choise and the string is well formated. the s-paramter formats the string in the following way: 2008-06-15T21:15:07.

Code Sample:

XPathNavigator form = MainDataSource.CreateNavigator();
XPathNavigator xmlPath =  form.SelectSingleNode("/my:Felder/my:Erstelldatum", NamespaceManager);
DateTime creationTime = DateTime.Parse(xmlPath.InnerXml);
DateTime MinDate = new DateTime(1900, 1, 1);

if (creationTime == MinDate)
{
     this.DeleteNil(xmlPath);
     xmlPath.SetValue(DateTime.Now.ToString("s"));
}

[1] http://msdn.microsoft.com/en-us/library/bb509311.aspx