.NET - Project And Solution Statistics

As a .NET programmer, we should know a few important statistics of the application we are working on. This ensures that the application is consistent in nature.

The below blog will cover:

• Prerequisites for this utility
• How to use this utility
• Results

As a .NET programmer, we should know a few important statistics of the application we are working on. This ensures that the application is consistent in nature. In an application with fewer projects it isn't difficult to get these statistics manually but in larger projects, it becomes an unproductive task, however still important. As an example, multiple team members may add new projects with varying .NET Framework versions, programming language version etc.. The initial version of this utility can help you generate these statistics in a second and in a consistent form.

1. You need .NET Framework version minimum 4.0.0 to run this utility.
2. You also need ‘command prompt’ window to view the result.
3. Dotnet solution file which has multiple projects in it.

Open the command prompt, go to the path where this utility executable is kept, and type Dotnetversion.exe

 

Press ‘Enter’ key.

About the application is displayed:

Press any key to continue.

Enter the Dotnet solution file path. If Solution file path is the same as a path where this utility Dotnetversion.exe file is kept simply press Enter, otherwise type the accurate path where a dotnetsolution file is kept, like D:\ABC\XYZ\ etc..

Once the solution file path is specified, the next option is to enter the Solution file name. Again, if only 1 file exists at the selected folder path simply press the ‘Enter’ key otherwise specify the solution file name. No need to specify the filename extension.

Once both the solution file paths and solution file names are given the stats collection processing will start.

Result

1. The stats will show how many projects the current solution had.
2. Programming language of the project, such as CSharp/VB.Net.
3. Programming language version. For CSharp projects, it can be like 4 or 5 or 6 etc. For Vb.net projects it can be 11 or 12 or 13 etc.
4. Dotnet framework version of the project
5. Project Filename
   
   

As an example, I executed a sample solution on my machine and both projects are .NET Framework 4.0 based.

Attached is the .exe file in this blog. Feel free to ask questions.