Visual Studio

Visual Studio 2015

Visual Studio 2015 has been released 😀 https://www.visualstudio.com A detailed comparison of the version is available here.

TFS Migration from On-Premise to Visual Studio Online

Having a server at home that hosts a TFS is nice. But really necessary? Not really. So I decided to move all my sources to Visual Studio Online. Visual Studio Online Basic is free for the first 5 users. That’s enough for me. The migration process is straight forward easy with a tool that is installed on my computer. The process is described here. Another post can be found here.

Building a Visual Studio project for SP2010/SP2013 (.NET 3.5/4.0)

In this post I will show you how you can use MSBuild to target your project for .NET 3.5 or .NET 4.0 and use a separate app.config file for each. My Warmup Tool is supposed to work with SP2010 and SP2013. To achieve that compatibility, I have to change the TargetFramework of the project to be able to compile, as well as the app.config so the application uses the desired Framework.

CKS – Dev for Visual Studio 2012 and 2013

The new release brings support for Visual Studio 2013 🙂 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

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.

What to know about the feature folder

One of the first things I used to tell guys new to SharePoint development is: Never ever name the folder of your feature “Feature1”. If you create a solution with WSPBuilder, or did some time ago with VS 2008, you have to rename the folders immediately! This is how a typical SharePoint project looks like, if you create features. I guess most of us have used the mighty WSPBuilder (http://wspbuilder.codeplex.com) for developing with SharePoint.

RSS feed for Knowledgebase Articles

The RSS Feed Product Index offers a feed with new KB articles for many products. SharePoint relevant feeds are: Access Services in Microsoft SharePoint Server 2010 Forefront Security for SharePoint SharePoint Administration Toolkit 3.0 SharePoint Designer 2007 SharePoint Portal Server 2001 Ok. I think this one can be skipped SharePoint Portal Server 2003 Still out there? Let’s migrate… SharePoint Server 2007 Windows SharePoint Services 3.0 SharePoint Server 2010 Some SQL feeds:

Visual Studio 2008 extensions for SharePoint v1.3

As you can read on the Microsoft SharePoint Team Blog, a new version of the Visual Studio extensions have been released. This version is Community Technology Preview. And wow… yes… finally… x64 support! The download is available here. The final release of VSeWSS 1.3 is planned for the North American Spring of 2009.Technorati Tags: SharePoint,VSeWSS

Great Sourcecontrol

Are you looking for a Sourcecontrol for your projects? Well, I was. Here is where I ended up: SourceGear Vault. It will store the your sourcecode in a SQL table, use the IIS for access, and brings along a client and Visual Studio integration. What could you want more? And the best of it, it is free!  Quote: Somebody said that Vault is free for a single user. Is this true?

Team Foundation Server 2008 and the SP1

Warning: Setting up the TFS is not an easy task. In our environment we have the Reporting Services and WSS installed on the TFS server. The TFS and SharePoint databases are on a separate SQL Server. Reporting Services databases are locally stored. If you now try to install the SP1, it will reconfigure your Reporting Services so that the databases are on the remote SQL Server. Of course that won’t work!

Visual Studio 2008 SP1 available

The SP1 is available through MSDN. See http://blogs.msdn.com/msdnsubscriptions/archive/2008/08/11/visual-studio-2008-service-pack-1-files-are-also-now-available.aspx and http://msdn.microsoft.com/en-us/vstudio/products/cc533447.aspx You will need it to install the Reporting Services 2008 add-in into your existing Visual Studio 2008 installation.Technorati Tags: Visual Studio,Visual Studio 2008

Webpart Development

Visual Studio Extensions If you want to write your own Webpart, you can start from scratch with a Class Library, or use the templates from http://www.microsoft.com/downloads/details.aspx?FamilyID=19f21e5e-b715-4f0c-b959-8c6dcbdc1057&DisplayLang=en The downside of this VS templates is, that they can only be used on a computer, which has SharePoint installed, and you cannot open a project created with the VS templates with a VS on which the templates are not installed. Server side controls Ishai Sagi wrote a great article about Webpart development.