Tag: VisualStudio2010

Ah, the good, old Visual Studio 2010! It was the first version of Visual Studio I used professionally in my day-to-day work. I’ve had to fire up Visual Studio 2008 every now and then due to legacy projects, though. Even VS2010 was a huge improvement over my earlier IDE experiences – I had been using Eclipse with WindowBuilder for Java projects, and Aptana Studio for PHP. Compared to them, VS2010 was surprisingly sleek and well-working experience!

Like so many other people, I feel like I did struggle with making SVN, SharePoint projects and VS work together, but that was a very occasional struggle.

Sequence contains more than one element

Launching a new debugger instance from code in Visual Studio

This post describes a quick solution to launching a new Visual Studio instance for debugging the code. There are a lot of applications for this, but where I’ve found it exceptionally useful, has been in debugging the Entity Framework’s code-first migration (one of the ways for database initialization) Seed-method. It is by default undebuggable, as when you are running Update-Database you can’t really use a -debug switch or anything, and there’s really no way to launch the debugger. Hence the best you can do is…Continue reading Launching a new debugger instance from code in Visual Studio

Visual Studio settings for "Track my active file in Solution Explorer" - a really useful setting to have enabled, if you ask me!

Tip: Scroll Solution Explorer to current file in Visual Studio 2012, 2013, 2015 and 2017

This quick post describes how to get the Solution Explorer to actually track your currently open file. For some reason, this extremely useful feature is disabled by default in Visual Studio. Enabling it helps you to better conserve your context, and see which part of your solution you’re in, while you’re developing a complex piece of software. Give it a try, in case you haven’t already! It’s great and extremely useful! :) Posts Related to “Tip: Scroll Solution Explorer to current file in Visual Studio…Continue reading Tip: Scroll Solution Explorer to current file in Visual Studio 2012, 2013, 2015 and 2017

SharePoint project properties

Visual Studio 2010 fails to show the design view of an aspx-page

This post is about solving the issue with Visual Studio 2010 failing to show the design view of an .aspx-page. Luckily, it’s an easy and pretty classical fix. Symptoms Whilst trying to view or edit an aspx-page in design mode within Visual Studio 2010, the window is just plain empty and there’s little you can do about it – selecting view markup or hitting F7 may not do anything, and restarting the Visual Studio doesn’t help. Solution The Design view requires a connection to the…Continue reading Visual Studio 2010 fails to show the design view of an aspx-page

Too long deployment path

Fixing the error: “The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.”

This post describes a few different ways of fixing the “The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.” error. One can encounter this issue when trying to package/publish a SharePoint solution, web site, or an Azure Webjob. Symptoms Visual Studio throws the following error when packaging a SharePoint solution to a .wsp file when deploying or publishing your web project (for example…Continue reading Fixing the error: “The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.”