VSIX visual studio extension in C# gets reset randomly

Question

0.00/5 (No votes)

See more:

I have a VSIX VIsual studio extension which is a tool window and has many progress bars and buttons. Clicking one of the buttons starts 5-8 worker threads on the background..This starts the 5-8 progress bar and shows the progress of the thread.

Occasionally I see that the progress bar on the thread reset randomly; its almost like a refresh of the ToolWindow and the progress go back to default state. I am not sure what is happening because there is no code that resets the progress bar to default state. The only explanation that I have is the app is crashing and recovering on GUI somehow. After the reset, some of the progress keep updating as if nothing happened continuing on from the reset state as if nothing happened (the worker threads keep running). I am at a loss to figure out what is going on. How can i troubleshoot this?

Have you seen this kind of issue in a Visual Studio extension that you developed where the GUI resets randomly?

What I have tried:

I have looked at crash exceptions. Nothing to report yet.

Posted 25-Jan-18 17:14pm

nitrous_007

Updated 29-Jan-18 11:44am

Add a Solution

Comments

johannesnestler 29-Jan-18 10:23am

Do you know how to debug a VS Extension (via experimental instance)?

nitrous_007 29-Jan-18 10:26am

Yes. It might be that in the worker thread work completed thread, I am not checking if error is not null . I added that. Before this I couldn’t identify a crash in the output log when I run and it only crashed once in a while so tough to debug.

johannesnestler 29-Jan-18 10:35am

So it seems to be a classic "threading and exceptions" problem...

nitrous_007 29-Jan-18 10:39am

It could be. Is that the normal behavior for VSIX tool for the tool window GUI to flash and reset so as to recover from the exception? This is my first time working with VSIX project.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

nitrous_007 · Accepted Answer · 2018-01-29T11:44:00

It was an exception that was unhandled. I should have used a different background worker for 2 different button click events- I accidentally used the same one and I was clicking both buttons.

I added below error detection and traced the error then.

void workerBuild_RunWorkerCompleted(object sender, RunWorkerCompletedEventArgs e)
        {
            if (e.Error == null)
             {     //Proceed as usual}
            else
             {   //print out error}
          }

{