Archive

Kategorien

Links

Andere Blogs




ITaCS GmbH

Aug 222013

CKS - Dev for Visual Studio 2012 and 2013

The new release brings support for Visual Studio 2013 Smile

The CKS - Development Tools Edition for Visual Studio 2012 and 2013 is a collection of Visual Studio templates, Server Explorer extensions and tools providing accelerated SharePoint 2010/2013 development based on Microsoft's SharePoint 2010/2013 development tools.

http://visualstudiogallery.msdn.microsoft.com/cf1225b4-aa83-4282-b4c6-34feec8fc5ec?SRC=VSIDE


Published: 8/22/2013  10:54 AM | 0  Comments | 1  Links to this post
Tagged as: Visual Studio, SharePoint

Jul 252013

Activating Features after Solution Deployment via VS

Visual Studio allow a F5 Deployment. I guess you all know that. The part where you have to think carefully is, when you add Features to your project.

Should you activate “Activate On Default”? Well, it depends (as always). Usually I don’t enable that setting, because features tend to be activated on scopes you won’t expect.

The problem

Take a WebApplication scoped feature for example. It might create SafeControl entries for your controls. Do you really want them to be added to an Extranet WebApplication if your solution is solely for an Intranet Application?

The problem does not exist for you, if you auto activate your features and have set your deployment configuration to “Default”. But in my case, I use “No Activation” and “Activate On Default = false” most of the time. Then, after you deploy an update of your solution, SharePoint retracts and re-adds the solution. The consequence is a deactivate feature Sad smile (in case of Farm and WebApplication scoped features).

My solution

CKS rocks! What’s that have to do with this?

The CKS Extensions for Visual Studio (http://cksdev.codeplex.com/) can Update the solution like you would do via PowerShell or stsadm with a new Deployment option named “Upgrade Solution (CKSDev)”.

image

Unfortunately CKS isn’t available for Visual Studio 2013 preview. So I had to do something else to avoid the problem with non activated features after deployment.

Fortunately Microsoft provided some Command Line action for post-deployment. And since the SharePoint URL is known from the properties of the project, it can be used via variable $(SharePointSiteUrl). Combined with stsadm to activate the feature, I had all I needed.

image

So for now, Deployment from VS will work again Winking smile


Published: 7/25/2013  8:44 AM | 0  Comments | 0  Links to this post
Tagged as: Development, Visual Studio, SharePoint, Solution

Jun 242013

Slow DFS Crawling in SharePoint

If you are indexing you DFS with SharePoint 2007/2010, you should take a look at this hotfix http://support.microsoft.com/kb/967671.

It addresses this issue “When you crawl the file shares in Microsoft Office SharePoint Server 2007 or Microsoft SharePoint Server 2010, you experience poor performance”.


Published: 6/24/2013  7:59 AM | 0  Comments | 0  Links to this post
Tagged as: SharePoint, Search, Hotfix

May 162013

SPQuery for my tasks

Developing solution with multiple languages (or a language which is not English) sometimes can be a bit painful. To configure a Webpart to display only my tasks, I would filter for [Me] or [Ich].

image

To achieve the same via code / CAML, you can filter by UserID and not the string “Me”.

  1: <Where>
  2:   <Eq>
  3:     <FieldRef Name="AssignedTo" />
  4:     <Value Type="Integer">
  5:       <UserID />
  6:     </Value>
  7:   </Eq>
  8: </Where>
  9: <OrderBy>
 10:   <FieldRef Name="Status" />
 11:   <FieldRef Name="Priority" />
 12: </OrderBy>
This is just a reminder for me, so I can find the information more quickly. But maybe this is useful for some of you as well Smile

Published: 5/16/2013  1:29 PM | 0  Comments | 0  Links to this post
Tagged as: Development, SharePoint, SPQuery