cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
rguggisberg
Active participant

Remove Error Tab Pop Ups in Visual Studio

Hi,

How do I disable the annoying tabs that InstallShield errors pop up in Visual Studio (see below)? It is sufficient that the errors appear in the Error List. These pop ups are disruptive in that it is hard to do anything else while the build is running.

Thanks.

InstallShieldError.png

Labels (1)
0 Kudos
5 Replies
Flexera Jenifer
Flexera

Re: Remove Error Tab Pop Ups in Visual Studio

Hi @rguggisberg ,

 

Since these are web-links,on clicking on the error-link you will be redirected to in-house web-page which gives detailed error description  in Visual Studio(VS2015 has this in-house web-renderer,VS2017 & later will launch separate web-page i guess).

I dont think so they will be popping in other scenarios.

 

If so can you confirm on what scenario it happens to you?

 

Thanks,

Jenifer

0 Kudos
rguggisberg
Active participant

Re: Remove Error Tab Pop Ups in Visual Studio

Hi Jenifer,

 

Any ISDEV error generates a popup.

Simple test is to just cancel the build to generate one.

The following is in the lo

ISDEV : error -32000: Build canceled by the user

Thanks,

Ron

0 Kudos
rguggisberg
Active participant

Re: Remove Error Tab Pop Ups in Visual Studio

Hi Jenifer,

Any ISDEV error or warning generates a popup.

The following is in the output window and log file as expected for a warning. What I need to do is disable the pop up.

ISDEV : warning -4371: There were warnings compiling InstallScript

Thanks,
Ron

0 Kudos
Flexera Jenifer
Flexera

Re: Remove Error Tab Pop Ups in Visual Studio

Hi @rguggisberg ,

 

I had tried this from our end,i think what you meant is  clicking on the error description it takes you to KB/community related web-page in VS.While on IDE, clicking on the description it doesn't take you anywhere.

 

Is that correct?

 

Thanks,
Jenifer

0 Kudos
rguggisberg
Active participant

Re: Remove Error Tab Pop Ups in Visual Studio

Problem solved by disabling 'Solution Error Visualizer' extension for VS.

 

 

0 Kudos