"Analyzing files [x of N]" gets triggered while building solution

Since this often leads to deadlocks: How can I tell (you) what is the
trigger?

I only found out so far that no single project alone is the cause but the
relationship of 2 projects (in a solution containing 20-30 projects):

Say project B uses project A:

  • I first rebuild the solution and wait for the triggered analyze process

(in toolwindow "Errors in Solution") to complete (which takes ages for ~40
very small files -- most time reanalyzing 100 files is done in half of this
time).

  • I make changes to project B and build project B: No reanalyze occurs

  • I make changes to project A and build project A: No reanalyze occurs

  • I just build project B (which depends on project A and therefore has to

be rebuildet): Project A is skipped (up-to-date), project B is built and
THEN a second later: reanalyze occurs.

--
/\/\arkus.

3 comments

Hello Markus,

How do you reference the projects in your solution? Do you add a reference
to a project directly or to the project's output assembly? Do you have web
projects in your solution? Could you please also check if turning off solution-wide
analysis (under ReSharper | Options | Code Inspection | Settings) helps to
avoid deadlocks? Thank you!

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Since this often leads to deadlocks: How can I tell (you) what is the
trigger?

I only found out so far that no single project alone is the cause but
the relationship of 2 projects (in a solution containing 20-30
projects):

Say project B uses project A:

  • I first rebuild the solution and wait for the triggered analyze

process
(in toolwindow "Errors in Solution") to complete (which takes ages for
~40
very small files -- most time reanalyzing 100 files is done in half of
this
time).

  • I make changes to project B and build project B: No reanalyze occurs

  • I make changes to project A and build project A: No reanalyze occurs

  • I just build project B (which depends on project A and therefore has

to
be rebuildet): Project A is skipped (up-to-date), project B is built
and
THEN a second later: reanalyze occurs.



0

Hello Andrew,

How do you reference the projects in your solution? Do you add a reference
to a project directly or to the project's output assembly?


All projects within the solution reference each other by direct project
references -- referencing the output assembly would break the debug/release
chain, wouldn't it?

Do you have web projects in your solution?


Yes, for WCF hosting:

( I don't remember the project type name, it's not the classic
"website"-project, but also directly hosted by an "ASP.NET Development
Server" instance ).

Could you please also check if turning off solution-wide
analysis (under ReSharper | Options | Code Inspection | Settings) helps to
avoid deadlocks?


Even "Pause Analysis" stops deadlocks from occuring.

But the deadlocks are not my point: The unneccesary re-analyze blocks and
heats my CPU for minutes, making VS-IDE response sluggish and the CPU fan
becoming loud.
So I really would like to get rid of the re-analysis of not-changed code:
Isn't there some option to log the trigger of re-analysis?

--
/\/\arkus.

0

Hello Markus,

Could you please check if removing the web project from a solution helps
to avoid files rescan when projects are built? We would also like to find
out more about those deadlocks. Could you please attach another instance
of Visual Studio with debugger to the hanging one, gather call stacks for
all running threads and attach this information here? Thank you!

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Hello Andrew,

>> How do you reference the projects in your solution? Do you add a
>> reference to a project directly or to the project's output assembly?
>>

All projects within the solution reference each other by direct
project references -- referencing the output assembly would break the
debug/release chain, wouldn't it?

>> Do you have web projects in your solution?
>>

Yes, for WCF hosting:

<ProjectGuid>{4DE70A37-EEE9-46AC-9282-E387F785B780}</ProjectGuid>

<ProjectTypeGuids>{349c5851-65df-11da-9384-00065b846f21};{fae04ec0-301
f-11d3-bf4b-00c04f79efbc}</ProjectTypeGuids>

( I don't remember the project type name, it's not the classic

"website"-project, but also directly hosted by an "ASP.NET Development

Server" instance ).

>> Could you please also check if turning off solution-wide
>> analysis (under ReSharper | Options | Code Inspection | Settings)
>> helps to
>> avoid deadlocks?

Even "Pause Analysis" stops deadlocks from occuring.

But the deadlocks are not my point: The unneccesary re-analyze blocks
and
heats my CPU for minutes, making VS-IDE response sluggish and the CPU
fan
becoming loud.
So I really would like to get rid of the re-analysis of not-changed
code:
Isn't there some option to log the trigger of re-analysis?



0

Please sign in to leave a comment.