Archive for February, 2010

XtCover is a Code Coverage Reporting tool created on top of VScodeCoverage Result to provide Flexible Reporting and Coverage Details.This is still beta but now released to Codeplex.Download the tool ,Play with it and provide your valuable feedback.For the next version we are accepting Invitation which ll use VS2010 and VS2010 Coverage Apis.

Today a Configuration Video was Uploaded which helps you understand the different Configuration you need to apply.Here is the  link


This Project is all about creating a re-usable asset libraries on SharePoint like re-usable web parts,solutions,workflows,Utilities targeting SharePoint applications .
Although this will contains re-usable assets ,the final deliverable will be an end-to-end solution which you can use for your enterprise.This is not going to be another CKS but we are going to target multiple aspects of an enterprise product.
We are going to use SP2010 as the primary platform (not MOSS-07)and going to add assets like Discussion-Forums,Silverlight Web parts ,calendars,Provisioning Solutions,Automated Solutions,Connectors,rollups and many more RIA and Web 2.0 features into this project.

Soon the Codeplex Project will be updated with many cool Web parts and utilities for SharePoint 2010 .

Here is the Link :-

Claim Identity Guide RC

Posted: February 14, 2010 in Uncategorized

C-Sharp faq (dynamic vs obejct):-

Posted: February 14, 2010 in Uncategorized

The csharpfaq blog for long  has been provided useful faqs for developers.While searching I stumbled upon the site again on dynamic vs object  and it provided a nice explanation .Read here .I would recommend to add this to your favorite:)

Enterprise Library5 and Unity 2

Posted: February 10, 2010 in Uncategorized

Code coverage Instrumentation using XtCover :-
Code coverage is a feature available in Visual Studio Team Edition for developers, testers and in Team suite also. Visual Studio uses block based statement (also known as C1 coverage) and condition coverage methodology. A block is commonly defined as a sequence of instructions that have a single entry point and a single exit point. We can consider an exit point to be a branch instruction, a function call, a return instruction or a throw instruction.
To get the coverage of source code, the test assemblies need to be instrumented by having MSTest.exe in place with MSBuild commands or through VSTS instrumentation options. Once the instrumentation is done the coverage file will be available for getting reports out of it.
VSTS is capable of opening the coverage file but if you want to open in some other reporting tool, you should convert the coverage file to the intended format of that reporting tool.
XTCover – An Intro
It stands for eXTreme COVERage, a web based .NET code coverage reporting tool. It provides the coverage summary in an enhanced way by using web technologies such as ASP.NET 3.5, Silverlight 3 to reveal very decent look and feel and user friendly navigation options. The main intention of this tool is that developers can be focused on the code areas where they should give more attention to increase the coverage of the source code.
The tool can be integrated with continuous integration process or leverage as a stand-alone coverage reporting tool. Besides that the tool is capable of automating MSTest coverage instrumentation process.The Primary goal is to present the Coverage results in a efficient and elegant way which VS Coverage does not provide.

Features of the tool
1. Capable of MSTest instrumentation and creation of coverage source based on required parameters (VSTS license is required)
2. Developers can choose their specific coverage source for reporting
3. Easy navigation to show coverage statistics, aggregates and graphs for module, namespace, class, method and line level
4. Tag cloud reports from module or package to class level
5. Source code display for respective classes and methods and highlighting covered / non-covered / partially covered lines of code
6. User will be focused to specific line level by selecting method names
7. Tool can be integrated with Continuous Integration process or can be used as a stand-alone product

We are working on the Next version of XtCover using the VS 2010 Profiling and instrumentation API and may be the next version will be entirely on SilverLight.

Visit the Codeplex Site for more details

Build and Release Framework: –
Build and Release Framework also know as Build Configurator can be utilized by project teams for incorporation of Continuous Integration (CI) in their daily workflow. In the world of Agile Software Development and Management process a robust build and Continuous Integration is a common requirement. This framework targets project based on .NET Framework 2.0 or higher.
Recommended tools include CC.Net , MSBuild, NUnit, MSTest, Stylecop, FxCop, NDepend, CAT.Net and Source Code repository (SVN, Clearcase and VSTS). We recommend projects to use MSBuild over NAnt, as MSBuild is well supported from Microsoft and future releases as well. Build scripts generated starting from VS 2005 onwards are MSBuild scripts which makes the build setup very easy for most projects. MSBuild version 3.5 & above has multiprocessor support for faster builds. However for heterogeneous projects NAnt might make for a better option.
Although the scope of Continuous Integration can vary from project to project, framework comprises of common minimum set of recommended tools. Project teams can extend the framework to add additional tools based on this initial setup with minimal effort.
High level features include:

  • Web based Continuous Integration Configuration tool to configure the Build Server
  • Get the latest source from the repository (SVN, ClearCase,VSTS)
  • Source Checkout
  • Source Versioning
  • Compile the source (MSBuild)
  • Build Trigger settings
  • Scheduled Trigger
  • Filter Trigger
  • Interval Trigger
  • Build the databases (SQL Server)
  • Database creation and updating data (such as creating tables, views, stored procedures etc. and updating the objects using SQL files)
  • Run Automate Tests & generate Code Coverage report
  • Run the unit tests (NUnit, MSTest)
  • Produce code coverage results (NCover, MS Code Coverage)
  • Perform Code Quality and security Checks using
  • FxCop
  • Style Cop
  • NDepend
  • CAT.Net
  • Create source documentation
  • Build MSDN style documentation using SandCastle
  • Email Notification
  • Dashboard of Build Status
  • Creation of MSI Packages
  • Perform IIS Activities
  • Creation of Virtual Directory and App pool
  • Publishing Web sites
  • Multi server Deployment

Functional View
Key functions of the system Includes as follows

  • Collect the user inputs to configure the Build and release framework
  • Automatically create the folder structure that includes Bin, Build Log, Build Settings, Src folder
  • Extracting the Project related tools and projects to the build setting folder
  • Automatically generate the MS Build script file based on user selection
  • Updating the CCnet configuration file
  • Update the ccnet dashboard view setup

For Details go to the Codeplex site here