If it's any comfort, VB.NET is having the same problems.

"As the project grows it becomes an excruciating experience. Now I
have a pure vb.net solution with two project at about 120
forms+classes+modules per solution. This is by far not the largest
project ment to be developed in vb.net 2005 (or is it ? :)"

MS reply:
"To address your specific question: the background compiler cannot
be turned off in Visual Basic .Net - it's actually the thing that's
providing all of the Intellisense information, formatting
information, and so on."

My guess, the resources needed to provide auto complete, undo etc.
grows with the project. At some point it becomes more than the
computer has to offer.


----- Original Message -----
Hi List:

I have recently upgraded to RB2006r1 from RB 5.5. After several days of finding the cause of Failed Assertion crashes and fixing those, I finally was able to get my app to compile. During this process, I found many things that totally surprised me...Please Note:

I have tested this with a G5 PPC, 1.8GHz with 1G RAM and a 2GHz Intel Core Duo with 1GB RAM. I tried it only one time on G4 PPC with 512MB of RAM. I opened the 5.5 project under RB2006r1, saved it under RB2006r1 and have used the saved project ever since.

When I began testing, all three systems had 10.4.4 on them and now all three have 10.4.5 on them. The results are just about the same, between the G5's with the Core Duo is a little faster, but not much. As for the G4, forget it...literally.

1) Under RB 5.5, the file size of my compiled app was 18 meg. I deleted 3 IF ELSE statements that were too long. These were the cause of the Failed Assertion crashes. This is the ONLY changes to my app. Now the file size of my compiled app is 29 MEG. The RB 5.5 project file size is 10.7MB. The RB2006r1 project file size is 14.4MB. The project file size GROWS every time I save it. I just now tested this again by opening the project, deleting a quotation mark and add it back again and save it. It grows from 14.4MB to 14.5MB and NOTHING is added but one quotation mark after I delete one quotation mark, just to have something to save. (Since this is a new one, I'll report this to feedback too). 2) Save times were slow but tolerable under 5.5, but now, they are at least 3 TIMES what they were. 3) Debug times are ridiculously SLOW, several times longer than 5.5, sometimes up to 4 full minutes. 4) Compile times are ridiculously SLOW, several times longer than 5.5, sometimes up to 4 full minutes.
5)  At times, during debug and compiles, ALL CPU and memory are used.
6) I get NUMEROUS spinning beachballs during debugs and compiles, for long periods of time. 7) After a build is completed, I literally have to close RB every time just to be able to run the built application, as memory is not being released.

Before writing this, I looked under RB Feedback and made a report, and looked on the list for others with similar problems. The ones I did find had the same complaints as these, but under RB2005, but I didn't see much in the way of any solutions for the problems.

Are there RB2006r1 users who have had this problem and found the reason for it? Are there things I can do to try to improve things? Or, is this just the way it is? Was there a fix that I missed?

I've been using RB for a long time and I expected some changes and problems migrating to RB2006, but I didn't expect anything like this. I would appreciate any help from anyone who has had this problem or RB.

Sincerely,


Mike Krugman
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>


--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 267.15.11/264 - Release Date: 2/17/2006


_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>

Reply via email to