For those of you who are using Resharper, version 8.1 was just released with Typescript support and better integration with Visual Studio 2013. The full release blog can be found here [http://blogs.jetbrains.com/dotnet/2013/12/resharper-81-goes-rtm-along-with-dotcover-dottrace/] . [http://blogs.jetbrains.com/dotnet/2013/12/resharper-81-goes-rtm-along-with-dotcover-dottrace/] With Resharper
To upgrade your existing MVC 4 application to MVC 5 you need to go through a number of steps to replace the references and patch the web.config [http://www.asp.net/mvc/tutorials/mvc-5/how-to-upgrade-an-aspnet-mvc-4-and-web-api-project-to-aspnet-mvc-5-and-web-api-2] . These steps are clearly explained in the original post, but when you're
> Update: Instead of using the Package Management Console, you can now use The Whack Whack Console [https://marketplace.visualstudio.com/items?itemName=DanielGriffen.WhackWhackTerminal] , ConEmu Integration [https://marketplace.visualstudio.com/items?itemName=DavidRoller.ConEmuIntegration] or BuiltinCmd [https://marketplace.visualstudio.com/items?itemName=lkytal.BuiltinCmd] for a better interactive console.
One of my team members shared his debug workflow for a set of executables that manipulate Exchange and CRM through webservice calls. This tool always needs to run in the context of a specific service account, even when debugging and testing against the development environment. A practice that needs changing,
Team Build by default creates 2 folders on your build agent: * 2010 * Sources * Binaries * TestResults * 2012: * src * bin * TestResults * 2013: * src * bin * tst These folder names were shortened as part of the 2012 release, partially to resolve "Path too long" issues with team build. But some of your
Scott Hanselman has blogged about using your local NuGet cache as your private local NuGet server in case your connection is down [http://www.hanselman.com/blog/HowToAccessNuGetWhenNuGetorgIsDownOrYoureOnAPlane.aspx] . And that works great when you're working locally. When working with Team Build you have multiple options, one is
By based on a Visual Studio User Voicerequest [http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2639467-make-alm-ranger-guides-available-on-msdn-and-ebook] and a lot of internal discussions we, the ALM Rangers, are proud to present our very first official ebook formatted guidance [http://blogs.msdn.com/b/willy-peter_schaub/archive/2013/05/29/better-unit-testing-with-microsoft-fakes-guide-a-la-mobi-and-epub.aspx?
By request of the audience, a link to the slide deck of our Techdays 2013 presentation on Better code through review and tools [http://www.microsoft.com/netherlands/techdays/SessionDetail.aspx?sessionId=3780] (in Dutch). There isn't too much useful information in the deck itself, since Thomas Huijer
There's a feature request on User Voice that requests Microsoft to bring back the "Create Unit Test" menu item which was removed in Visual Studio 2012 [http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2748862-add-create-unit-tests-menu-option-back-] . I've seen it come up as a potential Ranger solution
Today Microsoft publicly introduced the first Community Preview version of the Git tools for Visual Studio [http://blogs.msdn.com/b/bharry/archive/2013/01/30/git-init-vs.aspx] and the Team Foundation Service at the ALM Summit. Microsoft is fully committed to supporting this open distributed version control platform going
| | | Types inheriting from UITypeEditor | Recently I was asked to extend a Build Template for Team Build. There were a few fancy things which were required for this template, including picking files and folders in Source Control, selecting Work Items etc. I looked around the documentation on msdn.microsoft.com, but