This was a tool which was there in my mind since long but due to lack of time i couldn’t develope it. Finally i have come up with the tool and is available for free download.
Over time we have seen a lot of Lines of Code counter utilities for code written in .Net languages and other platforms in the market. Even though we have a lot of such or similar utilities I as an end user or developer always felt that the following were the main problems that haunted me if I wanted to do a quick lines of code analysis:
- There are so many of them out there that I was confused as to which one to use.
- Most of them didn’t even have a user manual.
- If one tool had a particular feature that I wanted, it would not have some other feature which would have helped me analyze the effort more accurately.
- Finally, I think one of the most sought after feature in any LoC counter utility, is the ability to export the analysis results into an excel file, which is a feature which not many LoC counter tools I have seen, provide.
Let me just give you a very brief introduction to the LoC counter tool that I have developed, for VS 2005 solutions and projects as well as for any C# or VB code files:
Instant Loc Analyzer is a simple .Net 2.0 windows application/tool that can be used to count the lines of code that make up a Visual Studio 2005 Solution, Project or C#/VB Code Files. The application can provide you valuable information like the number of designer generated lines of code in addition to providing the number of lines of code, the number of commented lines, the number of blank lines, and the total number of lines at a solution level, project level and code file level. It gives you the additional option of exporting the analysis results to an excel file.
Waiting for your comments and suggestions…..
The Guidance Explorer Development Team had conducted the Guidance Explorer customer satisfaction survey, which was opened on 28th June 2006 and closed on 9th August 2006. You can see a summary of the results on the Channel9 Wiki.
If you just quickly go through the results the following user concerns are evident:
Need to improve the guidance library through additional content and content types.
Need to integrate with Visual Studio.
Need to improve the UI to make the tool easier to use and more intuitive.
Need to update the guidance library automatically.
As put up on the site the summary of the results is: “The majority of respondents were happy with Guidance Explorer but not ecstatic. The biggest issues holding the tool back from true user enthusiasm are lack of library content and lack of automatic updates to content. Most respondents recognize the potential and would like to see the tool and library complete so they can use it in their development environment.”
Microsoft Office Word 2007 provides a new default file format called Microsoft Office Word XML Format (Word XML Format). The following extract from a MSDN article is a must read. It talks about how the package format decreases file size for Office documents.
The file format in Word 2007 consists of a compressed ZIP file, called a package. This package holds all of the content that is contained within the document. Using the package format decreases file size for Office documents because of the ZIP compression. The new format is also more robust to errors in transmission or handling. It allows you to manipulate the file contents using industry-standard ZIP-based tools. An easy way to look inside the new file format is to save a Word 2007 document in the new default format and rename the file with a .zip extension. Double-click the file to open and view its contents.
If you are confused with terms like GAT and GAX, this one is for you:
The Guidance Automation Extensions (GAX) expands the capabilities of Visual Studio 2005 by allowing architects and developers to run guidance packages, such as those included in Software Factories, which automate key development tasks from within the Visual Studio environment.
The Guidance Automation Toolkit (GAT) is an extension to Visual Studio 2005 that allows architects to author rich, integrated user experiences for reusable assets including frameworks, components and patterns. The resulting Guidance Packages are composed of templates, wizards and recipes, which help developers build solutions in a way consistent with the architecture guidance.
Microsoft has been talking about software factories for some time now, but now we see that they are indeed coming out with some really cool stuff on that front. As i would like to put it: “The factory is smoking”. I know its a bad line :). In one of my previous entry’s i had talked about Smart Client Software Factory. Recently Microsoft patterns and practices group has come out with the Web Service Software Factory. The Service Factory is the latest addition to the fast-growing crop of factories, including the Smart Client Software Factory and the Mobile Client Software Factory.
Using the Web Service Software Factory, developers and architects can build more consistent, higher quality distributed systems with less effort. The Service Factory is based upon a robust layered architecture and includes written and automated guidance that spans all layers of a service including the service interface, business logic and data access logic.
Tom Hollander has written a nice entry on Web Service Factory on his blog. Do read it. In order to download the service factory and read about the same visit the following link:
Download (Right now only C# version of the same is available, but you can expect the VB.Net version to come out soon)
A common question isn’t it? I am sure that most of us are tired of answering this question time and again. What really happens is that when you have lots of logic in the UI layer; the code in the UI layer of an application becomes very difficult to test without either running the application manually or maintaining ugly UI runner scripts that automate the execution of UI components. While this is a big problem in itself, an even bigger problem is the reams of code that are duplicated between common views in an application. It can often be hard to see good candidates for refactoring when the logic to perform a specific business function is copied among different pieces in the UI layer. Reusability and Maintainability are the two major factors which force us to use a specific design pattern while developing an application.