We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

.NET outside of Visual Studio

Formal Metadata

Title
.NET outside of Visual Studio
Title of Series
Number of Parts
170
Author
License
CC Attribution - NonCommercial - ShareAlike 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
As a .NET developer when you write code you write that code in Visual Studio. That has been the De facto standard since the origin of .NET. Does it have to be that way? Today we have alternatives like Monodevelop (Xamarin studio) and Sharpdevelop. For the last two years or so I have been writing all my .NET code in regular text editors like vim and sublime. There are several benefits to working this way. In this talk we will dive into: - How and why you would want to do your work outside of Visual Studio. - The good and the bad of the .NET environment - How this affects the way you write and organize code - Busting some of the myths behind developer productivity