imageThis summer has been one of the most productive I’ve ever had. Normally I spend summers balancing frozen margaritas in my hammock. That’s called Hammock Driven Development. You should try it.

Visual Studio 2013 Preview was released in June at the //build/ conference. I was there giving a talk about the brand new HTML editor, Browser Link and Web Essentials. Here’s the story of my road to //build/  and Visual Studio 2013.

Starting early

Mikhail, Todd and Alex, all developers on the web editors crew, started working on a new HTML editor for Visual Studio 2013 last summer before we shipped Visual Studio 2012. The codename for this new editor was Libra. My zodiac sign happens to be Libra, so I thought it was a fantastic name.

The HTML editor was based on WebMatrix’ HTML editor, which was much newer and all written in C#. The old HTML editor in Visual Studio was a mix between C++ and C#. It was old. From the nineties actually. It also had dependencies on FrontPage. Yes, FrontPage.

We went through all aspects of the editing experience to create the best HTML editor in the world. That meant scrutinizing every little detail till we got it just right. The formatter was the most challenging piece from a UX point of view. We spent months getting it perfect. I had no idea something so seemingly simple could be such a challenge.

The formatter was just one piece of the puzzle. Another big piece was the validator. Our test engineer, Van, had for a while wanted to learn Python. So when we needed a big pile of real-world HTML documents for testing, Van decided to teach himself Python, write a web crawler and download thousands of web pages to validate against. The guy is not normal.

Libra is a huge project and we’re not done yet. We’ll never be done – the HTML editor will continue to evolve.

Visual Studio Update 1

While work continued on Libra, we were preparing for the first update to Visual Studio 2012. This update became very important, because this was the first time we introduced new modern web languages to Visual Studio. It was a great day when we shipped both CoffeeScript, LESS and KnockoutJS Intellisense in Visual Studio Update 1.

For me, this marked the day when Visual Studio entered into the modern web arena full force. Not only that, we actually shipped both CoffeeScript and LESS several months earlier in Web Essentials. The cadence of which we were able to get valuable technology in the hands of web developers was unprecedented at Microsoft it seemed.

Two other very popular features from Web Essentials was also promoted into Visual Studio Update 1 – Paste JSON as Classes and Handlebars syntax highlighting. This was a good release.

Shortly after the release, Peter was able to join the Libra effort while Mikhail moved on to another team at Microsoft. We now had all the developers on the web editors crew working full time on Libra.

Up until this time, Libra was the only project we had started working on for Visual Studio 2013. But that was about to change.

The Eureka crew

Back in October 2012 I took over as program manager for the Eureka crew. Eureka was the codename for Page Inspector, which was a feature first introduced in Visual Studio 2012. I now had the responsibility for both the web editors and Page Inspector.

I’ve always found the technology behind Page Inspector fascinating, so this was pretty exciting to me. Long before I joined the Eureka crew, I had been trying to figure out how to move Page Inspector out of Visual Studio and into the browser, but was never able to nail the right user experience. I just knew it had to live in the browser somehow.

After an evening of Ballmer Peaking with Sayed, all the pieces started to fall into place – a true eureka moment in fact. The next day I sent a mail to my boss, wherein I pitched Artery – the codename for what was to become Browser Link. The email went out February 25th, 2013.

The Eureka crew couldn’t start working on it just then. We had to finish the work on Page Inspector for Visual Studio Update 2 first. It wasn’t until April before Dan and Joe started coding on the proof of concept. At this point, we didn’t even know if it was technically possible, let alone if we were even able to make it in time for Visual Studio 2013.

We did make it, but for the June release Browser Link was very far away from being feature complete. We basically shipped the proof of concept. As you can see from this video, we’ve come a long way since then. Browser Link is going to change everything.

Side Projects

During Christmas time last year, both Sayed and I were each building a website. He built one for his new MSBuild book and I built one for Web Essentials. We gave each other tips and tricks and decided to put them all online. In January 2012 we introduced the Web Developer Checklist. It got leaked before it was done and made the front page of Hacker News on a Sunday night. We had to hurry up and finish it right then.

In June we then released the Web Developer Checklist Chrome extension, which helps web developers test their websites for best practices. Many of the items on the checklist is currently being built into Web Essentials as Browser Link extensions, so now there’s full Visual Studio integration as well. It’s funny how things progress and evolve over time. From website, to Chrome extension, to Browser Link extension.

This happened at the same time I was working on a new blog engine for ASP.NET called MiniBlog. The idea was to see how simple I could write a modern blog engine with the latest technology. Exactly the same as when I started BlogEngine.NET many years ago. I used MiniBlog as part of the demo in my //build/ talk.

Leading up to //build/, I also started porting Web Essentials from Visual Studio 2012 to 2013 Preview. It was a bigger task than I thought, but it was done in time to release at //build/. It was even used in the keynote which I was very proud of.

Now both Web Essentials 2012 and 2013 are open source and have already taken community contributions. That’s fantastic and I’m very grateful for everyone who have pitched in so far. Thanks!

In July, Sayed and I finally started working on a project we had talked about doing for months. We wanted to make it easy for anyone to create and share Visual Studio item- and project templates. The project is called SideWaffle Template Pack and is an open source community extension for Visual Studio 2012 and 2013.


Now summer is over and Visual Studio 2013 RTM is almost ready to ship. I hope you’ll have as much fun using it as we had making it.

Comments

Ben McCallum

Thanks for all your hard work (and the team). FYI, I had a similar idea for a new blog engine that could be install-able via a NuGet package. It would add a new area to an mvc site (views and theme would then be easily customisable) and the business logic code wrapped up in dependencies (dlls) backed by a SQL CE database. Will take a look at MiniBlog now and see if u were on a similar tact. I hate that there is no nice mvc blogs out there that can be added and integrated into sites. Would love to chat further about it all.

Ben McCallum

Jim Killeen

I've attended some of your conference sessions and have followed your great work on Web Essentials and I'm really glad you're out there constantly trying to make things better. Keep it up.

Jim Killeen

Ivan Mladenovic

"So when we needed a big pile of real-world HTML documents for testing, Van decided to teach himself Python, write a web crawler and download thousands of web pages to validate against. The guy is not normal." Why is he not normal ? Python is all purpose great programming language , easy an fun to learn.

Ivan Mladenovic

Mads Kristensen

Ivan, it was a joke. Learning a new language and use it to build a web crawler is not normal. It's totally awesome

Mads Kristensen

Terrence

Mads, great work on the html editor. Can you tell me why the c# { braces do not indent with the html indention? It seems odd that they stick out to the left of the html. I would like the c# code to indent the same as the HTML.

Terrence

Mads Kristensen

Terrence, we've been working on Razor formatting all the way up to RTM. There's a lot of improvements over what was shipped in RC

Mads Kristensen

angol tata

"CoffeeScript, LESS and KnockoutJS Intellisense" big kudos!

angol tata

Steve Ognibene

That's an amazing year, Mads. Congratulations!

Steve Ognibene

Raju Golla

Thanks for sharing the journey & deploying best features in VS 2013. Would like to read similar non-tech articles.

Raju Golla

Brian Davis

Hi Mads, You had done great work for Visual Studio! and keep up the great work. Seems like your website now runs on your MiniBlog? and no longer BlogEngine.Net? Do you see MiniBlog features being added to BlogEngine.Net anytime soon? I really like BlogEngine.Net and you and the BE team had done great work with it and would like to see it continue to run for many more years to come :) Keep up the great work, and also like your demo videos. Have a great day! Brian Davis

Brian Davis

Mads Kristensen

Brian, yes this site now runs on MiniBlog. It's unlikely that BE will take any code from MiniBlog. They are not compatible. MiniBlog will never be as full featured as BlogEngine and I'd not recommend people using MiniBlog. It's too simple and lacks basic features. BlogEngine is your best bet

Mads Kristensen

Ron

Nice to read. Well done. Now i know what to do this summer if i boredom :p

Ron

Patrick

@Mads - SideWaffle seems like an awesome idea, but what if I want to have a subset I don't want to share with the world but I do want to share between my team? Is it possible? http://stackoverflow.com/questions/19571109/sidewaffle-create-your-own-template-set-to-share

Patrick

Mads Kristensen

Patrick, I answered your question on StackOverflow

Mads Kristensen

Telemedicine

Hi, Mads. congratulations. your articles really nice.

Telemedicine

Comments are closed