at System.Windows.Forms.Control.get_Handle()
at System.Windows.Forms.Control.set_Cursor(Cursor value)
at SourceGearLLC.VaultVsipClient.VsipClientChangeSetView.VsipBusyStateChanged(Boolean busy) in E:\Builds\Vault7.0.0.x_Nightly\vault\src\VaultVsipClient\VsipClientChangeSetView.cs:line 31
at SourceGearLLC.VaultVsipClient.VaultVsipClient.SetBusy() in E:\Builds\Vault7.0.0.x_Nightly\vault\src\VaultVsipClient\VaultVsipClient.Implementation.cs:line 309
at SourceGearLLC.VaultVsipClient.VaultVsipClient.AutoRefreshBegin() in E:\Builds\Vault7.0.0.x_Nightly\vault\src\VaultVsipClient\VaultVsipClient.Implementation.cs:line 362
at VsipLib.VsipIdeGuiClientInstance.AutoRefresh() in E:\Builds\Vault7.0.0.x_Nightly\vault\src\VsipLib\VsipIdeGuiClientInstance.cs:line 61
at VaultClientPresentationLib.GUIClientInstance.TimerCallback(Object sender)
Cross-threading exception in vault standard 7.0
Moderator: SourceGear
-
BrianFairchild
- Posts: 7
- Joined: Tue Oct 08, 2013 2:18 pm
Re: Cross-threading exception in vault standard 7.0
We could use more information.
What actions were you doing in Vault when this happened?
Were you using Vault Client or Visual Studio? Was this information in the client/VS or in their log files?
If using Visual Studio, what version?
What actions were you doing in Vault when this happened?
Were you using Vault Client or Visual Studio? Was this information in the client/VS or in their log files?
If using Visual Studio, what version?
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
-
BrianFairchild
- Posts: 7
- Joined: Tue Oct 08, 2013 2:18 pm
Re: Cross-threading exception in vault standard 7.0
Sorry, I should have provided more info.
I'm working on integrating the API into our own in-house vs.net add-in. This seems to occur when I'm not doing anything at the time, but after I've taken some action such as committed a file with a comment. Seems like it's at least a minute or so after an action, I'll have to see if I can recreate it and time it. But it does seem to be inconsistent right now. I do also have the Vault Standard VS Enhanced Client installed and active at the time.
There's not anything in the log file except notifications of login/logout events.
----10/22/2013 9:12:06 AM bfairchild--::1(::1)--SSL Disabled Login
----10/22/2013 9:12:14 AM bfairchild--::1(::1)--SSL Disabled Logout
----10/22/2013 9:12:58 AM bfairchild--::1(::1)--SSL Disabled Login
----10/22/2013 9:13:03 AM bfairchild--::1(::1)--SSL Disabled Login
----10/22/2013 9:13:54 AM bfairchild--::1(::1)--SSL Disabled Logout
----10/22/2013 9:13:54 AM bfairchild--::1(::1)--SSL Disabled Logout
----10/22/2013 9:13:54 AM bfairchild--::1(::1)--SSL Disabled Login
----10/22/2013 9:13:56 AM bfairchild--::1(::1)--SSL Disabled Login
VS.Net 2008.
I'm working on integrating the API into our own in-house vs.net add-in. This seems to occur when I'm not doing anything at the time, but after I've taken some action such as committed a file with a comment. Seems like it's at least a minute or so after an action, I'll have to see if I can recreate it and time it. But it does seem to be inconsistent right now. I do also have the Vault Standard VS Enhanced Client installed and active at the time.
There's not anything in the log file except notifications of login/logout events.
----10/22/2013 9:12:06 AM bfairchild--::1(::1)--SSL Disabled Login
----10/22/2013 9:12:14 AM bfairchild--::1(::1)--SSL Disabled Logout
----10/22/2013 9:12:58 AM bfairchild--::1(::1)--SSL Disabled Login
----10/22/2013 9:13:03 AM bfairchild--::1(::1)--SSL Disabled Login
----10/22/2013 9:13:54 AM bfairchild--::1(::1)--SSL Disabled Logout
----10/22/2013 9:13:54 AM bfairchild--::1(::1)--SSL Disabled Logout
----10/22/2013 9:13:54 AM bfairchild--::1(::1)--SSL Disabled Login
----10/22/2013 9:13:56 AM bfairchild--::1(::1)--SSL Disabled Login
VS.Net 2008.