Strange Issue with all of the 4.5 builds

I have noticed a strange occurrence that only happens if I have one of the
4.5 builds installed. Every time that I open VS (VS2005), a silent install
of some sort is kicked off. (I.E. msiexec is running). This runs for about
5 mins, during which time all keystrokes within VS are ignored. After this
stops, then VS acts normally. The funny thing is that mouse actions work as
expected.

Has anyone else seen this behavior?

David


6 comments

Hello,

Looks like the advertised components behavior (like MSO's "install on first
use"), but R# itself does not use advertisement for any of the components
it installs. Could be that we touch some of the Visual Studio packages or
some third-party COM component involved in Visual Studio startup, which uses
the Windows Installer to install-on-demand or automatic self-repair.

If you could use ProcMon to log the file activity on behalf of the msiexec
processes, we could have a guess on what it's doing.


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0

Is there a specific set of processes that you want captured? In a small
attempt to capture the interaction between VS2005 and msiexec I captured
well over 4GB of activity. This could not be sent to anyone - it exceeds
the size of our mail servers.

David

"Serge Baltic" <baltic@intellij.net> wrote in message
news:dc0986bf136be98cb56dcc342b618@news.intellij.net...

Hello,

>

Looks like the advertised components behavior (like MSO's "install on
first use"), but R# itself does not use advertisement for any of the
components it installs. Could be that we touch some of the Visual Studio
packages or some third-party COM component involved in Visual Studio
startup, which uses the Windows Installer to install-on-demand or
automatic self-repair.

>

If you could use ProcMon to log the file activity on behalf of the msiexec
processes, we could have a guess on what it's doing.

>

-
Serge Baltic
JetBrains, Inc - http://www.jetbrains.com
"Develop with pleasure!"

>



0

One piece of information that may help with this issue. This only occurs
when first updating a file in the Web Site.

The solution that we have currently has 10+ class libraies plus an ASP.NET
web site (not a web application). I had been updating one of the class
library assemblies since opening VS this morning. MSIEXEC did not kick off
until I attempted to update the code-behind class of one of the user
controls in the web site, several hours after opening VS.

David
"David Williams" <daviddwilliams@earthlink.net> wrote in message
news:gneg8c$3ri$1@is.intellij.net...

Is there a specific set of processes that you want captured? In a small
attempt to capture the interaction between VS2005 and msiexec I captured
well over 4GB of activity. This could not be sent to anyone - it exceeds
the size of our mail servers.

>

David

>

"Serge Baltic" <baltic@intellij.net> wrote in message
news:dc0986bf136be98cb56dcc342b618@news.intellij.net...

>> Hello,
>>
>> Looks like the advertised components behavior (like MSO's "install on
>> first use"), but R# itself does not use advertisement for any of the
>> components it installs. Could be that we touch some of the Visual Studio
>> packages or some third-party COM component involved in Visual Studio
>> startup, which uses the Windows Installer to install-on-demand or
>> automatic self-repair.
>>
>> If you could use ProcMon to log the file activity on behalf of the
>> msiexec processes, we could have a guess on what it's doing.
>>
>> -
>> Serge Baltic
>> JetBrains, Inc - http://www.jetbrains.com
>> "Develop with pleasure!"
>>
>>
>



0

This is still occurring as of build 1206. It appears that the offending
component mix is Resharper vs Infragistics 6.3.

David

"Serge Baltic" <baltic@intellij.net> wrote in message
news:dc0986bf136be98cb56dcc342b618@news.intellij.net...

Hello,

>

Looks like the advertised components behavior (like MSO's "install on
first use"), but R# itself does not use advertisement for any of the
components it installs. Could be that we touch some of the Visual Studio
packages or some third-party COM component involved in Visual Studio
startup, which uses the Windows Installer to install-on-demand or
automatic self-repair.

>

If you could use ProcMon to log the file activity on behalf of the msiexec
processes, we could have a guess on what it's doing.

>

-
Serge Baltic
JetBrains, Inc - http://www.jetbrains.com
"Develop with pleasure!"

>



0

Hello,

This is still occurring as of build 1206. It appears that the
offending component mix is Resharper vs Infragistics 6.3.


That could well be that we're triggering some COM component of that Infragistics
pack that needs MSI configuring (or maybe it's just doing a self-repair to
keep fit). We'll investigate if there's anything to be done.


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0

As an update - this turned out to be a problem that R# actually found - the
installation of the Infragistics controls was in error and R# was actually
causing the installer to kick off in an attempt to repair the installation.
A full reinstall of Infragistics cleared the issue.

David

"Serge Baltic" <baltic@intellij.net> wrote in message
news:dc0986bf139cf08cb726c54ee34a0@news.intellij.net...

Hello,

>
>> This is still occurring as of build 1206. It appears that the
>> offending component mix is Resharper vs Infragistics 6.3.
>

That could well be that we're triggering some COM component of that
Infragistics pack that needs MSI configuring (or maybe it's just doing a
self-repair to keep fit). We'll investigate if there's anything to be
done.

>

-
Serge Baltic
JetBrains, Inc - http://www.jetbrains.com
"Develop with pleasure!"

>



0

Please sign in to leave a comment.