/Community

I put in four hours of testing with build 1.0.77 for VS2003.

I have only one significant problem to report, a recommendation, and some KUDOS.

---- Problem -------------

While I have tested various builds before 1.0.77, this is the first time I tested it with a large Visual Studio project (88,000 lines of code).

The significant problem is how long it takes for it to parse a project that size and how log it takes for CodeIt.Once tasks that do cross project replacements e.g. Rename.

It took 40 minutes to initially parse the project.

It took 4 or more minutes to Rename.

Computer used has 1 GB of RAM, 1.60 mhz Pentium 4 processors.

------- Recommendation ---------

Enable the Finish button on the Encapsulate Field wizard's Preview step window.

Unlike the other wizards, the Encapsulate Field wizard's preview step window doesn't allow the user to click the Finish button at the Preview step. (It's disabled.) Instead one must used the Back button to go to the previous ttep and press the Finish button there.

-------- KUDOS -----------------

CodeIt.Once for VS2003 was rock solid for me this test cycle.

Installation was trouble free and quick.

I tested every refactoring feature except Decompose Conditional, and Undo over and over again. Everything work correctly every time.

The wizards screens are now outstanding. Excellent asthetics AND super explanations of each refactoring operation. The progress bar in the left panel of each wizard is cool.

This has been a decent product from the first build I tried. It is now an outstanding product in every respect except the large project issue I reported above.

I hope to put the latest VS2005 build through rigorous testing in the near future. If it is as good as the VS2003 version it appears you are about ready for RTM.

Thank you for the compliments - it is very important for us to know your opinion! I'm glad you liked the wizard UI option - that was the major change in the last couple of months and I'm happy it is well accepted.

Re ------- Recommendation ---------
Yes, this makes perfect sense and that's how it was supposed to work. We actually found couple of bug in the Encapsulate Field wizard when you were troubleshooting the Finish button issue. Thanks!

Re ---- Problem -------------
There might be some external process that affected your large project test. I have seen CodeIt.Once working really slow couple of times on my machine but both times I found a "System" process that was hogging my CPU.

There are "progress" messages in the VS status bar - can you tell me which of the 2 below take long time?

"Parsing [solution name]..."
"Loading reference [assembly name]..."
"Caching [assembly name]..."

We are doing performance testing on a regular basis to make sure the product provides acceptable speed. We have two projects for that - one is 60,000+ lines (2.6MB) and the other is 8.1MB

Here is our performance data on a computer that is just slightly faster than yours (2.4 GHz P4):

Project 1
---------
Size - 60,000+ lines, 2.6 MB in 210 .vb modules
Loading references (first time) - 17.2 sec
Loading references (second time) - 2.99 sec
Parsing - 9.9 sec

Total (first time) - 17.2 + 9.9 = 27.1 sec
Total (second time) - 2.99 + 9.9 = 12.89 sec

Project 2
---------
Size - 8.1 MB in 1185 .cs modules
Loading references (first time) - 18.7 sec
Loading references (second time) - 3.55 sec
Parsing - 18.5 sec

Total (first time) - 18.7 + 18.5 = 37.2 sec
Total (second time) - 3.55 + 18.5 = 22.05 sec

Late last week we redesigned the way we load the reference metadata and now "Loading References" works _twice_ faster (will have a build available soon) - the performance data above before the redesign.

Also, one thing to remember, that the reference metadata is loaded only when you open project first time - it is being cached and on the second run the references load much faster - about 4-6 times.

---

Thank you,
Serge Baranovsky
http://submain.com - .NET Developer Tools  |  Microsoft VB MVP  |  http://vbcity.com - VB Developer Community
» » (Static Code Analysis + Automatic Refactoring) / Painless Coding Guidelines = CodeIt.Right - http://submain.com/codeit.right
» » C#/VB .NET Coding Guidelines - FREE 100+ page ebook (PDF) http://submain.com/guidelines