Manifesto for Agile Software Development

Agile Manifesto Development What about Agile Methodologies? Is Agile (SCRUM) still popular in big software projects? Do we still have to implement bicycle with new name for software development process? I think nope, because  we are uncovering better ways of developing

software by doing it and helping others do it Through this work we have come to value: Individuals and interactions  over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. More...

More productive with Visual Studio Toolbox. All in one code framework.

All in one code frameworkCode samples, code framework, how to find them with Visual Studio and bring them to the product. Senior Project manager Mei Liang show how to use code framework and what customer can do with it. Free centralized, customer driven library. Online support services provide typical samples available for developers to help them resolve typical tasks. Frequently questions analyzed and provided as free code samples. You also can ask for code sample from Microsoft. Over 600 samples can be found in 2 places: code-plex and MSDN. Just download visual studio extension from Tools menu Search Code sample inside Visual Studio. Just highlight code and right click then search code sample and it will give you highlighted API examples. The Microsoft All-In-One Code Framework is a free, centralized code sample library driven by developers' needs. Our goal is to provide typical code samples for all Microsoft development technologies, and reduce developers' efforts in solving typical programming tasks. More...

Debugger canvas

Debugger canvasDebugger Canvas is a new user experience for the debugger in Visual Studio Ultimate. It pulls together the code you’re exploring onto a single pan-and-zoom display. As you hit breakpoints or step into code, Debugger Canvas shows just the methods that you’re debugging, with call lines and local variables, to help you see the bigger picture. Code debugging with code bubble is easy now! :) If object change state we can see updates easily. The Debugger Canvas is built on technologies that only ship with Visual Studio Ultimate, such as IntelliTrace and the code analysis features in the Architecture tools. More...

vNext - Microsoft Visual Studio 2011 IDE features

VS 2011vNext – is new version of Visual Studio 2011. First article about features was created by Weston Hutchins - Program Manager, Visual Studio IDE Platform Microsoft Corporation 19 May 2011. I am going to discuss new features presented by VS2011 IDE  vNext presentation in this article. What is cool about brand new 2011 Visual Studio? It is more organized, clean, nice look and feel. If you with VS 2011 it can save a lot of time, it is busy a lot of toolbars and buttons, especially in debugging. You can do each thing in different ways. For example search and replace changed from Find and Replace -> Find symbols -> Navigate to, few examples how to do same thing in new VS 2011 in demo from channel 9 below. Challenge for vNext release is simpler (reducing amount of buttons, setting UI to concentrate on your code) + faster (overall responsiveness, long running operations, memory utilization and better feedback / telemetry) = more productive. Project is fully supported between 2011 and 2010 solution projects.

Simpler + Faster = More Productive More...

What is Build Verification Testing (BVT) ?

BVT Build Verification Test is a set of tests run on every new build to verify that build is testable before it is  released to test team for further testing. These test cases are core functionality test cases that ensure application is stable and can be tested thoroughly. Typically BVT process is automated. If BVT fails that build is again get assigned to developer for fix. In software testing, a Build Verification Test (BVT), also known as

 Build Acceptance Test, is a set of tests run on each new build of a product to verify that the build is testable before the build is released into the hands of the test team. The build acceptance test is generally a short set of tests, which exercises the mainstream functionality of the application software. Any build that fails the build verification test is rejected, and testing continues on the previous build (provided there has been at least one build that has passed the acceptance test). More...