Terje Sandstrom

------ Chief Software Geek at Inmeta Consulting in Scandinavia ----- and a Visual Studio ALM MVP

  Home  |   Contact  |   Syndication    |   Login
  55 Posts | 1 Stories | 82 Comments | 0 Trackbacks

News

Subscribe

Delicious Save this on Delicious Visual Studio Feeds

¨

Tag Cloud


Article Categories

Archives

Post Categories

Image Galleries

Company stuff

Interesting bloggers

Interesting companies

Microsoft

Microsoft Norge

Microsoft Regional Directors

Microsoft Test

MSFT Blogs

MVP

NNUG

Other interesting stuff

TFS

Visual Studio

MTM

Microsoft Test Manager
Go to Part 1 – List of Product Updates for information on Visual Studio and TFS 2012 updates Looking for the VS 2010 extensions ? Go to Visual Studio 2010 - List of Product Updates (Part 1) + Extensions (Part 2). Looking for links to the test adapters, go to this blog post. UPDATE Aug 18th 2013: Updates: Visual Studio Tools for Git, TypeScript, ReSharper, TFS Power Tools, Code Contracts, Build Manager, Web Essentials, Code Contracts, tangible T4 editor , Just Decompile, DotPeek ADDED: Inmeta AssociateRecentWorkItems ......

Download from VS Gallery In my work I meet many developers, tester and project managers, all using Visual Studio. When I ask them if they have updated it to the latest version, there are many who simply don’t know. Should you always update ? YES, you should. The Visual Studio development teams are continuously making improvements to the product. The question also often comes when we notice that something doesn’t quite work the way it should, and we then realize it is caused by not having the latest ......

This post is continued HERE. Go to Part 1 – List of Product Updates for information on Visual Studio and TFS 2012 updates Looking for the VS 2010 extensions ? Go to Visual Studio 2010 - List of Product Updates (Part 1) + Extensions (Part 2). Looking for links to the test adapters, go to this blog post. UPDATE Aug 18th 2013: Updates: Visual Studio Tools for Git, TypeScript, ReSharper, TFS Power Tools, Code Contracts, Build Manager, Web Essentials, Code Contracts, tangible T4 editor , Just Decompile, ......

UPDATED Apr 15th 2013: Corrected to VS2012 Update 2 UPDATED Mar 23rd 2012: Added information about VS 11 UPDATED Mar 21st 2012: Added info and link to VS/TFS 11 tool for getting the Test Attachment Cleaner, now included with the TFS Power Tools UPDATED Mar 17th 2012: Added sql queries for TFS 11 Beta. Changed structure after Adam’s advices. Updated information. UPDATED Jan 9th 2012: Added link to SQL 2008 R2 SP1 CU4 for ghost file fix Background Recently there has been several reports on TFS databases ......

This post is about VS 2010, go here for the VS/TFS 11 extensions. UPDATED Apr 9th 2012: VersionInfo, NuGet, Code Contracts UPDATED Oct 7th 2012: New Visual Studio GDR UPDATED Aug 31th 2012: New versions updated of ReSharper, NDepend, Web Essentials, Community Build Manager, Code Contracts (March 2012), NuGet, ILSpy, DotPeek, Just Decompile, tangible T4 editor, LinqPad. Added the VersionInfo tool, so you know you have the latest update of VS 2010 UPDATED April 20th 2012: New version of NuGet manager. ......

Update: These have been superseded and included in later Cumulative Updates. See http://wblo.gs/cu8v for checking what you got and updates, or download the tool. Also see info about the updates and extensions here.During the summer Microsoft has released two important hotfixes for the Testing tools. These two hotfixes solves 7 serious problems: # Issue solved Fix in : 1.1 Appdomain error when running a test agent on a computer with Visual Studio installed 1) 1.2 Exception with search error may happen ......

Sometimes the tool is blamed for errors which are not the fault of the tool – this is one such story. It was however, not so easy to get to the bottom of it, so I hope sharing this story can help some others. One of our test developers started to get this message inside the test steps part of a test case in the MTM. saying “Could not load file or assembly ‘0 bytes from System, Version=4.0.0.0,……..” The same error came up inside Visual Studio when we opened a test case there. Then we noted a similar ......