Issue 44 in gurtle: COM error after commit

[codesite...@google.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 44 by tortoise...@gmail.com: COM error after commit
http://code.google.com/p/gurtle/issues/detail?id=44

Two times now I got this error after a commit:

Completed : At revision: 234
Error : Failed to start the issue tracker COM
provider 'Gurtle'.
Error : Unknown error 0x80131509
Error : Operation is not valid due to the current state of
the object.

But this only happens if I don't open the issues dialog from the TSVN
commit dialog first.
I'm using the very latest version of Gurtle (compiled myself) from trunk
(and of course the latest version of TSVN).

I'm not sure if this is an issue of Gurtle or TSVN yet. But the COM error
indicates that there's some kind of exception thrown from Gurtle.

Don't have the time right now to investigate, so I'm opening this issue so
I don't forget.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[codesite...@google.com]

Comment #1 on issue 44 by azizatif: COM error after commit
http://code.google.com/p/gurtle/issues/detail?id=44

> only happens if I don't open the issues dialog from the TSVN
> commit dialog first

Where else in TSVN can you open the issues dialog from?

> Operation is not valid due to the current state of
> the object.

This is definitely something coming from a .NET Framework exception, as its
the
standard message for for System.InvalidOperationException. It would be
great if you
can help to determie the steps to reproduce this.

[codesite...@google.com]

Comment #2 on issue 44 by tortoise...@gmail.com: COM error after commit
http://code.google.com/p/gurtle/issues/detail?id=44

I've analyzed the problem:
In plugins.cs, line 182, Gurtle throws an InvalidOperationException if the
project
isn't set. But the project variable is only set if the issuebrowserdialog
is shown
before.
Since sometimes I do a commit without assigning an issue to it and
therefore without
first showing that dialog, I then get the error at the end of a commit.

TSVN shows the error only since I've implemented reading the COM error
description,
it didn't show that error before because the error string variable that
gets returned
by OnCommitFinished() is empty, so TSVN had nothing to show.

[codesite...@google.com]

Updates:
Status: Started
Owner: tortoisesvn
Labels: Milestone-Release1.0

Comment #3 on issue 44 by tortoise...@gmail.com: COM error after commit
http://code.google.com/p/gurtle/issues/detail?id=44

(No comment was entered for this change.)

[codesite...@google.com]

Updates:
Status: Fixed
Mergedinto: -

Comment #4 on issue 44 by tortoise...@gmail.com: COM error after commit
http://code.google.com/p/gurtle/issues/detail?id=44

This issue was closed by revision r224.