| T O P I C R E V I E W |
| Wrongway |
Posted - Oct 25 2007 : 10:20:04 AM
I noticed in the newer version (1561) that the parsing is taking longer than in previous versions. Every time I start VS2003 (which has 114 projects) it is taking around 20-30 minutes to parse.
I would think that within the parsing DB there would be a Date/Time for when that file was last parsed, if there is a different DTG than what is within the DB, then re-parse that file. This would speed up loading the projects.
Also, is there a way to trap on the save message within VS to re-parse when you save the file, this way the DB is always up to date.
Just my two cents.
Larry |
| 6 L A T E S T R E P L I E S (Newest First) |
| Wrongway |
Posted - Oct 25 2007 : 4:19:54 PM
Done... It is 1319 and the parsing is now complete... Wonder what it will be once I reboot! It also parsed all the MFC junk too. |
| sean |
Posted - Oct 25 2007 : 3:58:05 PM
2 hours! 5 minutes should be sufficient for most large solutions.
Please use this form:
http://www.wholetomato.com/support/contact.asp
put topic 6858 in the subject.
please paste into the message body the number of files in your solution and also the system info from the VA options dialog (use the copy info button below the info display).
|
| Wrongway |
Posted - Oct 25 2007 : 3:37:55 PM
Trying the 1614, loaded it around 1035. Its 1236 and still parsing! I also realize that the first time loading after an install takes some time. The box that this is installed on is a 64-bit piece of *@%^&*@! |
| Wrongway |
Posted - Oct 25 2007 : 1:39:16 PM
The solution is a mixture of .NET (C#) along with MFC/C++. |
| sean |
Posted - Oct 25 2007 : 1:10:50 PM
If your solution is a managed solution with .Net/assembly references from one project to another, you definitely want to use 1614. |
| feline |
Posted - Oct 25 2007 : 12:08:14 PM
You may find the current beta helps:
http://forum.wholetomato.com/forum/topic.asp?TOPIC_ID=6848
Certainly it contains a number of changes to speed up parsing of .NET code.
If you have:
VA Options -> Performance -> Parse all files when opening a project
this is likely to have some bearing on the situation, but turning it off impacts alt-g.
Approximately how many files do you have in the solution? OFIW dialog shows this on the title bar.
You may find that disabling the IDE's intellisense - a single zero length read only NCB file in the solutions root directory is enough in VS2003 - will help. VS2003's intellisense parser is much less resource intensive than VS2005's, but it still has an effect. |
