File Path On Footer Extension 1.4.3 released with Environment Font support.

File Path On Footer Extension version 1.4.3 released with Environment Font Support.

Tools->Options->Environment->Fonts and Colors->Environment Font

Sample screenshot with custom Environment Font setting

Change log

Version 1.4.3

  • Fixed – Invalid Exception message while copying file path using right click.
  • Fixed – File path was not properly visible (bottom area was cropped) if we change the Environment Font settings.

Version 1.4.2

Fixed – Unwanted exception message was showing on Web Essentials Preview Pane of .LESS file.
Version 1.4.1

Fixed – underscore (_) was not showing in file path.
Version 1.4

Fixed font change in Conditional Breakpoint window.
Fixed an issue in .sql file.
Exception handlers are updated to show detailed error descrition, if any.
Version 1.3

Fixed Invalid text in Conditional Breakpoint and Quick Watch window.
Version 1.2

Added support to 11 Visual Studio Themes
Version 1.1

Added support to more files.
Version 1.0

Initial Version

Click here to Download

If the tool helps you and you like it please rate it!

File Info (File Properties Window) Extension for Visual Studio

This lightweight extension lets you display the file properties window by a single click from Visual Studio’s Editor. This tool can be accessed from bottom right corner of the File Editor.. Read More

File Properties Window directly from Visual Studio IDE

Interested to see how to create an extension like this then read “Getting started with Visual Studio Editor Viewport Adornment Extensions” from CodeProject.com.

File Path On Footer Extension 1.4.2 released with Fixes.

I just released File Path On Footer Extension version 1.4.2 with some fixes, Change log is given below for your reference.

Change log

Version 1.4.2

Fixed – Unwanted exception message was showing on Web Essentials Preview Pane of .LESS file.
Version 1.4.1

Fixed – underscore (_) was not showing in file path.
Version 1.4

Fixed font change in Conditional Breakpoint window.
Fixed an issue in .sql file.
Exception handlers are updated to show detailed error descrition, if any.
Version 1.3

Fixed Invalid text in Conditional Breakpoint and Quick Watch window.
Version 1.2

Added support to 11 Visual Studio Themes
Version 1.1

Added support to more files.
Version 1.0

Initial Version

Click here to Download

File Path On Footer Extension for Visual Studio

Visual Studio “14” CTP now available

Some hours back , the Visual Studio “14” CTP was released. An early preview of the next version of Visual Studio. You can find the Visual Studio and .NET release announcements on Soma’s blog. You can find a complete list of new features in the Visual Studio “14” CTP knowledge base article.

This Visual Studio “14” CTP brings together several new technologies that we recently announced including:

  • The .NET Compiler Platform, also known as “Roslyn,” which includes the upcoming version of our managed compilers for C# and VB as well as an API that enables developers to integrate with the VS compiler and language service more easily than they can today. You can read more about the .NET Compiler Platform on the C# and VBteam blogs.
  • Updates to the Visual C++ Standard Library, added utility functions, manipulators, functions, and several bug fixes that will improve productivity. To learn more about all the changes visit the C++ team blog.
  • Tooling for ASP.NET vNext. ASP.NET vNext is a lean and composable .NET stack for building modern web applications for both cloud and on premises servers. For more information about ASP.NET vNext go to ASP.NET vNext website and check out the ASP.NET team blog.

CTPs provide early adopters with an opportunity to try out the new and improved product features, and the ability to share feedback with the product team.

Please report bugs using Connect and share your suggestions through Send-a-Smile from within the IDE or on our UserVoice site.

Note, Visual Studio side by side support is not available on this early build. Do not install this CTP on a machine with any other version of Visual Studio installed.

What is exactly One ASP.NET?

There was a common question from all the corners, as a .NET developer what  would be the project template  that you are going to use for your web application. The answer would simply WebForms if the question was raised prior to the introduction of ASP.NET MVC.

Since the release of the ASP.NET MVC Framework in 2009, the developers had a major choice to make when starting up a new project: Web Forms or MVC?

What if I want to use both? What if a third choice comes along like Web API, SignalR ?

Microsoft has finally brought these components all together, and the result is One ASP.NET.

ASP.NET MVC Web Forms Web API Signal R all together

One ASP.NET

One ASP.NET helps in Unified Dialog and made the web app to use Web Forms , Web API, MVC together, and also came with some cool Scaffolding features etc.

Starting with Visual Studio 2013,  there is now only one web project type in Visual Studio.

One ASP.NET Project TypeWhen you choose this project type to start with, you will be propmpted with additional configuration options begin working with your project.

One ASP.NET - New Project

If you look closely, you’ll see a new set of check-boxes which will allow you to include the folders and core references for other technologies outside of the major one that you selected.

Choose Reference Items - One ASP.NET

 

As per your project template and checkbox selection all the necessary configuration and directories will be done for you automatically. Now when you attempt to add a new item to your project, the options lists just about everything you could think of.

One ASP.NET Add New Item

You might be interested in video “Introducing One ASP.NET” by Scott Hunter.

 

ASP.NET MVC Release History, Supported Visual Studio versions and .NET Framework

ASP.NET MVC is a web application development framework built on top of Microsoft’s .NET Framework. ASP.NET MVC framework is a lightweight, highly testable presentation framework that is integrated with existing ASP.NET features.

Here I’m listing down the ASP.NET MVC versions and its release dates,

ASP.NET MVC version history , release dates, supported visual studio and .net frameworks

Let us see the stable ASP.NET MVC versions and its supported Visual Studio versions ( and .NET Frameworks ) together,

ASP.NET MVC 1 – Visual Studio 2008 and Visual Studio 2008 Service Pack 1 (.NET Framework 3.5)

ASP.NET MVC 2 – Visual Studio 2008 and 2010 (.NET Framework 3.5, 4.0)

ASP.NET MVC 3 – Visual Studio 2010 (.NET Framework 4.0)

ASP.NET MVC 4 – Visual Studio 2010 Service Pack 1 and Visual Studio 2012 (.NET Framework 4.0, 4.5)

ASP.NETMVC 5 – Visual Studio 2013 (.NET Framework 4.5, 4.5.1)

Integrated Color Picker for Visual Studio IDE.

Integrated Color Picker for Visual Studio Integrated Color Picker for Visual Studio IDE.

This tool will very useful if you are working as a Web Developer or UI designer, who mainly uses Visual Studio for the day to day assignments.

This tool offers the below options,

  • Color Selection from Color Canvas.
  • Color Selection from Available Colors.
  • Color Selection from Standard Colors.
  • Color Selection from Saved Colors.
  • Color Selection using Eyedropper.

Integrated Color Picker for Visual Studio

Read more from Color Picker Page

Error List Manager 1.1 is available with more export options

I just released Error List Manager 1.1 with new Export templates. In this version new HTML and PDF templates are added.

Read more from Error List Manager page.

Supported HTML Templates

Below listed HTML files are generated using different ELM HTML Templates.

Export Visual Studio's Error List as HTML

Export Visual Studio Error List as HTML

Export Error List from Visual Studio

Export Visual Studio's Error List as HTML

Save Error List from Visual Studio Error List Toolwindow

Supported PDF Templates

Export Visual Studio' Error List as PDF

Email

Using this option you can directly send the Error List items as an attchment in Outlook email client. If oulook is already running then make sure that Visual Studio and Outlook runs with same access rights.

Emailing Visual Studio's Error List using ELM

Print

This option will send the Error List to the default printer. You can change any default settings from Print settings window as per your requirement.

Printing Visual Studio's Error List using ELM