dotEASY Community

Subscribe to dotEASY users mailing List

Mailing list members click here

Click here to see dotEASY ALPHA 2 bugs

  Send us your feedback

Download a zip file with a solution that implements some validation classes

In this page we will publish the comments of dotEASY users, if you want to send us a comment  click here.

The dotEASY Team is gratefull with all the users that sent us yours comments, also with the web sites that mentioned our project.

Thanks to all !!!

Web sites that mentioned the dotEASY project:

Users comment's:

Kevin Amerson 1

Kevin Amerson 2

Luca Minudel 1 (Setup Problems)

Luca Minudel 2 (Comments)

Luca Minudel 3 (Bugs)

Kevin Amerson 1

Hello!

I am using alpha 2, got an email this morning... wonderful job! this is a really nice addin for visual studio.  I am more concerned with tracking application progress than making automatic code changes.  To that end, a few more features would be really nice:

- Export the metrics analysis to an xml file.

- Is there a way you could do an overall ""quality"" rating? and then explain the quality rating based on the metrics:

""Class1 has an overall quality rating of 77 out of 100.  This is based on distant package Instabilities of no more than .1 and no less than .9, etc... The biggest areas of improvement would be: fewer dependances from packages, increasing comment to code ratio, etc...""

Overall this is an excellent tool as it is!  I'll continue to provide feedback as I have time to analyze my core project with this.

Thank you!

dotEASY Team response

Kevin, First, thanks for trying our product.
 
Answering your questions:
 
    - (XML) When you generate a Metric Report or an Advice Report a html page is generated, also a xml file is generated in the same directory of the html with the     analysis.
 
    - (Quality Rating) For the second point "Quality rating" you can create code smells with thresholds that tells to the user the quality rating of a class. For example, create a code smell named "High quality" and add a threshold with the Inestability metric with a value upper of 80 (for example).
Then you can create others code smell with other ranges of a metric
Other solution is to develope a simple code smell validation that query the metric value of a code element (for ex. a class) and tells to the user the quality of the code element.
 
Some project's comments
 
 This is an academic project and these version will finish with the automatic code changes framework. It have a lot of details to improve (for example some metrics are not being calcuted ok). Briefly we'll publish the metrcis that are not ok.
 
These changes and other new functionallity we will do if we found investors, because it requires a lot of time. To realease the final version we have been working very hard for one year.
 
Thanks again

Kevin Amerson 2

Wow! thank you for the quick respone.

I still need to spend more time with your product, but yes please feel free to publish any of my comments on your site, or any future comments as well.

I also wanted to comment on the speed, your application is very fast, impressive over some of the other code tools that I've used to analyze my project.

This type of tool is very important is lacking in the community, thank you for developing it! and I'll continue to send you feedback.

Kevin

Luca Minudel 1 (Setup problems)

Hi all,

I'm luKa and I'm going through an exam of Software Engineering and I'm doing a project for the course. I'd like to use and try your dotEasy tool to collect some metrics from the code I wrote for the project but I got some trouble during setup.

I'm using Windows2000 Server SP3, MS .NET Framework 1.0 SP2, VS.NET

After setup the Add-In didn't start in VS.NET, when I mark it to start

from Add-In manager I had "Class not registered" error.

So I registered the Add-In dll with regasm (without /codebase because  the assembly is not strong named). After that the dotEasy sub-menu in the Tool menu appeared but when I select any dotEasy sub-menu item nothing happen.

Can you help me?

dotEASY Team response

Hi Luca,

 First of all, we?d like to thank you for trying our software and for posting this problem. We have discovered that this problem is rather common when it comes to program addins. I'm sendig you an alpha version, which calculates all the metrics. If you don?t mind, I would like to ask

you to fill the questions that are located in our page. I would also like to ask you to send a brief comment of what yo think about dotEASY, its GUI and everything you consider worth of comments.

Thanks in advance

Luca Minudel 2

 Luca Minudel 3 (Bugs)

dotEASY Team response are in red

 It work now, Thanks!

 Right now I'm collecting some metrics with dotEasy about code  maintainaility (analyzability, changeability and stability) and soon I

 will fill the questionnaire!

 I've found some bugs (I think they are bug but... I don't know dotEasy   requisites/specifications so maybe I'm wrong). Here they are:

 - BUG

 Function: menu dotEasy/Configuration/Reports

 Action: configure reports option and click Accept button

 Error: System.UnauthorizedAccessException: Access to the path  "d:\program files\doteasy team\doteasy\MetricReport.xml" is denied.

 Note: I'm developing with a non administrator user, and I've  installed dotEasy with the administrator user.

In the installation you have the option to install for the current user logged in or to all users.

 - BUG

 Function: SetUp

 Action: Check for setup for "All Users" (not just me)

 Error: dotEasy Add-Inn is not installed/enabled for other users  other then Administrator

 Work-around: Repair the installation from the development user.

 Note: I'm developing with a non administrator user, and I've  installed dotEasy with the administrator user.

Idem.

 - BUG ?

 Metric: CA Afferent Coupling (of a namespace)

 Error: Does not consider usage of static members.

In the testing phase we found problems with this metric. So, please don't use it.

 - BUG ?

 Metric: CE Efferent Coupling (of a namespace)

 Error: In a namespace it report a value bigger then the total  number of classes defined in the namespace

Note: in the metric description you mention of counting 'using'  sentence; but in C# 'using' keyword  (as in C++) just merge the name-space in the current  name-space it does not imply usage or even  accessibility (and it's possible to reference a class in  another namespace without the 'using':  with full name); and there is also a different usage of  'using' keywords: just to define an alias

 (using sys = System;).

In the testing phase we found problems with this metric. So, please don't use it.

 - BUG ?

 Metric: NOC Number of Classes (of a namespace)

 Error: Does not count classes with only static members.

We will review this metric, but in the testing phase we didn't find errors

 - BUG ?

 Metric: NOTE Number of Exported Types (of a namespace)

 Error: In the metric description you mention "...available for  clients defined outside the namespace" but visibility in C# is about Class and Assembly and not  Namespace. Indeed it calculate a wrong value.

The description, says Description: Total number of classes and interfaces of a namespace that are available for clients defined outside the namespace. It can also be defined as the total number of non-internal classes and interfaces of a namespace

It reffers to the number of public classes of a namespace, these classes could be used in another namespace

 - BUG

 Metric: Number of Types

 Error: Does count Enums? It should.

 Error: Does count classes with only static members? It should .

 Note: Compare with ILDASM statistic value TypeDef (subtract 1 from  TypeDef... it's bugged too!)

The metric NOT (number of types) it counts all types (enum, class, struct, interface), with any kind of members.

Then you can use variants of this metric, Number of abstract Types (NOTa) , Number of Concrete Types (NOTc) , Number of Exported Types (NOTe) , Number of Classes (NOC)

 - BUG

 Metric: Number of Classes

 Error: Does count nested classes? It should.

It should be counting nested types

 Ciao, Luca