index > Visual Studio Guidance Automation Toolkit > Loading solution verty slow

Loading solution verty slow

Hi,

After having developed a package and tested ok on a medium-sized solution (6 projects), we notice a very slow loading of a bigger solution (32+ projects with several subfolders each).

Setting the BindingRecipeRun="false" in the .gpState file does not seem to help.

The loading takes 15 minutes easily...

Any ideas on what could be causing this delay and how to remedy this ?

Thanks in advance,

Michel Liesmons.

mliesmons Tuesday, August 08, 2006 12:48 PM

Hi Michel,

Try clearing the entries in the History Tab (if there are too many) under Guidance Navigator Window. This could be the culprit most of the times. Its pretty tedious to clear the entries one by one (I wish there was a clear all option :) ), but its worth it.

Regards,

- Santhoo

SanthoshMReddy Tuesday, August 08, 2006 1:07 PM

Hi Michel,

Regards,

- Santhoo

SanthoshMReddy Tuesday, August 08, 2006 1:07 PM

Thanks Santhoo, loading went down to +/- 2 minutes, still slow but possibly acceptable.

Funny though, since the list only contained about 10 entries, and when enabling for the first time on a machine, it took those 15 minutes too...

kr,
Michel.

mliesmons Tuesday, August 08, 2006 2:01 PM

It may be related to those entries checking for their enable state as the solution opens...

kzu Tuesday, August 08, 2006 3:04 PM

That's what I thought too, but enabling 1 or 20 entries did not seem to make that much of a difference. And after all, all that happens in there is checking for the target-type and its name...

kr,

Michel.

mliesmons Wednesday, August 09, 2006 12:07 AM

I have the same problem with *.gpState.

Hasanybody found a way to fix it?

Alexey Raga Saturday, August 12, 2006 10:08 AM

If you have GAX References that take long to run, keeping the list in the History tab short will help loading times as you will be reducing the need for probing solution elements.

vga Friday, September 01, 2006 9:03 PM

Did it all... still sloooow

TeddyCineas Wednesday, September 06, 2006 4:10 AM

I had the same problem with a solution using CAB automation. It occurred whenever the solution being opened was included in VSS as well.

The fix is a recompile of the Guidance Automation for CAB (SmartClientDevelopment) after commenting out the line refreshing the vsProject variable in the ContainsReference method of the ViewTemplateReference class in the GuidancePkg solution distributed for CAB.

Hope this helps, Rob

private bool ContainsReference(Project project, string referenceIdentity)

{

if (project.Name == referenceIdentity) return true;

VSProject vsProject = (VSProject)project.Object;

//vsProject.Refresh();

foreach (Reference reference in vsProject.References)

{

if (reference.Identity == referenceIdentity) return true;

}

return false;

}