Visual Studio

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

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.

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.

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

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.

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.

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:

A quick test shows that the just released Visual Studio 2010 works on my SP 2010 Beta 2 VM. I could open a project, hit F5 to deploy it and debug successfully.

I’ve just seen that the RC is available via MSDN. Silverlight 4 is not supported in the RC it says in the notes. Have to try SharePoint Development against the Beta 2…

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