search

google-code-export / mb-unit

Automatically exported from code.google.com/p/mb-unit
0 stars 0 forks source link

Gallio Reloads once for every assembly changed #493

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. have a large project with many assemblies
2. Load Gallio on the project, clear "Auto Reload Assemblies"
3. change a low layer assembly, causing many other assemblies to recompile
4. Each assembly that pops up saying it changed and asking to reload will 
cause a reload of the project, even though responding to all the dialogs 
was completed before the first reload was done.

What is the expected output? What do you see instead?
It should only do one reload after all changes have been noticed.
It does one reload per module changed, even if that means running multiple 
reloads in a row after all changes and reload dialogs are done.

What version of the product are you using? On what operating system?
MbUnit/Gallio 3.0.6 build 787

Please provide any additional information below.
If you don't clear "Auto Reload Assemblies", you get the same result, but 
you can't compare the number of changed modules to the number of reloads 
as easily.

Original issue reported on code.google.com by NetRateS...@gmail.com on 4 Aug 2009 at 3:07

GoogleCodeExporter commented 9 years ago 
Ok, so we should probably add a little delay before prompting the first time, 
then we
should collapse all pending change events to eliminate redundant reloads.

Original comment by jeff.br...@gmail.com on 4 Aug 2009 at 8:31

GoogleCodeExporter commented 9 years ago

Original comment by jeff.br...@gmail.com on 4 Aug 2009 at 8:31

GoogleCodeExporter commented 9 years ago 
We do wait for a second before triggering the reload, but either that isn't long
enough or there's a bug lurking in there somewhere. I'll have a look.

Original comment by grahamr...@gmail.com on 2 Sep 2009 at 6:33

GoogleCodeExporter commented 9 years ago 
How many reloads do we trigger?  Suppose a reload is already in progress and 
some other files hange, 
do we coalesce the remaining reload requests or queue them?

Original comment by jeff.br...@gmail.com on 2 Sep 2009 at 7:29

GoogleCodeExporter commented 9 years ago 
This is really annoying, because when you include two files of a large project 
it
reloads after the first file was changed. When Visual Studio then tries to 
compile
the other (maybe after compiling some other stuff meanwhile) it can't do it, 
because
the file was blocked by Gallio.

Original comment by straufl@gmail.com on 19 Nov 2009 at 8:15

GoogleCodeExporter commented 9 years ago

Original comment by Yann.Tre...@gmail.com on 17 Jul 2010 at 8:20

GoogleCodeExporter commented 9 years ago

Original comment by Yann.Tre...@gmail.com on 14 Jun 2011 at 5:53