fissum Work Item Rss Feed

Commented Issue: TFS server is reported as offline even when reachable through VS2010 [31895]

johnnyjob — Fri, 29 Jun 2012 15:15:25 GMT

The TFS Server I use is listed in the Fissum menu, but is marked as offline, even though it's open in VS2010. I choose Connect, but that does not work. I've tried both the ClickOnce and Standalone install.
Comments: ** Comment from web user: johnnyjob **

I had similar problem. I downloaded sources and started a debug session. It turned out that my TFS server has some queries which don't work, and these queries throw the following exception even if you run them via Team Explorer:
TF51011: The node specified is not found in the classification hierarchy. The error is caused by "path_to_your_query".

Obviously a work-around to this issue is to make all queries in all team projects in your TFS runnable.

I also can commit a fix which just removes queries which don't work from Fissum UI.

Commented Issue: TFS server is reported as offline even when reachable through VS2010 [31895]

jessehouwing — Thu, 26 Apr 2012 20:52:09 GMT

Which TFS version are you using and which Visual Studio version are you using (incl service pack version)?

Fissum 1.0 should work with TFS 2010 and VS2010. Fissum 1.0.1 was compiled against the 2010 SP1 version.

Created Issue: TFS server is reported as offline even when reachable through VS2010 [31895]

christ — Wed, 07 Dec 2011 14:54:51 GMT

Created Issue: unhandled exception when i attempt to connect to my TFS server [31863]

rpaint01 — Wed, 30 Nov 2011 20:50:19 GMT

2011-11-30 10:39:09,886 [4] WARN Fissum.TrayApp.Model.TPCModel - Cannont update TPC
Microsoft.TeamFoundation.WorkItemTracking.Client.ValidationException: TF51011: The node specified is not found in the classification hierarchy. The error is caused by «'Encore Development\Release 1\Sprint 1'».
at Microsoft.TeamFoundation.WorkItemTracking.Client.Query.Initialize(WorkItemStore store, String wiql, IDictionary context, Int32[] ids, Int32[] revs, Boolean dayPrecision)
at Fissum.TrayApp.Model.QueryModel..ctor(QueryDefinition definition, ProjectModel projectModel, String path)
at Fissum.TrayApp.Model.ProjectModel.FillQueryHierarchyCore(QueryFolderModel vmFolder, QueryFolder tfsFolder)
at Fissum.TrayApp.Model.ProjectModel.FillQueryHierarchyCore(QueryFolderModel vmFolder, QueryFolder tfsFolder)
at Fissum.TrayApp.Model.ProjectModel.FillQueryHierarchyCore(QueryFolderModel vmFolder, QueryFolder tfsFolder)
at Fissum.TrayApp.Model.ProjectModel.FillQueryHierarchy()
at Fissum.TrayApp.Model.ProjectModel..ctor(Project project, ProjectConfiguration configuration, TPCModel tpcModel)
at Fissum.TrayApp.Model.ProjectModel.GetProjetModel(Project project, ProjectConfiguration configuration, TPCModel tpcModel)
at Fissum.TrayApp.Model.TPCModel.FillProjectList()
at Fissum.TrayApp.Model.TPCModel.UpdateTPC()
2011-11-30 10:39:15,972 [3] ERROR Fissum.TrayApp.Model.TPCModel - tfs: authentication failed: The remote name could not be resolved: 'tfs'
System.Net.WebException: The remote name could not be resolved: 'tfs'
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.TeamFoundation.Proxy.BisRegistrationServiceProxyWsdl.GetRegistrationEntries(String toolId)
at Microsoft.TeamFoundation.Proxy.BisRegistrationProxy.GetRegistrationEntries(String toolId)
at Microsoft.TeamFoundation.Proxy.BisRegistrationService.RefreshMemoryCache()
at Microsoft.TeamFoundation.Proxy.BisRegistrationService.RefreshDiskAndMemoryCacheIfNeeded(Boolean direct)
at Microsoft.TeamFoundation.Proxy.BisRegistrationService.RefreshCachesIfNeeded(Boolean direct)
at Microsoft.TeamFoundation.Proxy.BisRegistrationService.GetRegistrationEntries(String toolId)
at Microsoft.TeamFoundation.Framework.Client.PreFrameworkServerDataProvider.FindServiceLocation(String serviceType, String toolId)
at Microsoft.TeamFoundation.Framework.Client.PreFrameworkServerDataProvider.LocationForCurrentConnection(String serviceType, Guid serviceIdentifier)
at Microsoft.TeamFoundation.Client.TfsConnection.EnsureProviderConnected()
at Microsoft.TeamFoundation.Client.TfsConnection.<Authenticate>b__1()
at Microsoft.TeamFoundation.Client.TfsConnection.UseCredentialsProviderOnFailure(Action action)
at Microsoft.TeamFoundation.Client.TfsConnection.Authenticate()
at Fissum.TrayApp.Model.TPCModel.Connect()

Closed Issue: TSWA button active but not functionnal [30807]

Miiitch — Tue, 07 Jun 2011 10:40:41 GMT

Button is active even if the TSWA service in TFS is not configured
Comments: Resolved with changeset 89781.

Created Issue: TSWA button active but not functionnal [30807]

Miiitch — Tue, 07 Jun 2011 09:06:45 GMT

Button is active even if the TSWA service in TFS is not configured

Closed Issue: Fissum can't find TeamExplorer configuration for a 2008 server [30798]

Miiitch — Mon, 06 Jun 2011 08:39:11 GMT

Comments: Resolved with changeset 89747.

Created Issue: Fissum can't find TeamExplorer configuration for a 2008 server [30798]

Miiitch — Mon, 06 Jun 2011 08:38:42 GMT

Closed Issue: Fissum crashes when I try to open the work item in TSWA if the workitem is new [30771]

Miiitch — Sun, 29 May 2011 21:03:50 GMT

Comments: Resolved with changeset 89435.

Created Issue: Fissum crashes when I try to open the work item in TSWA if the workitem is new [30771]

Miiitch — Sun, 29 May 2011 21:03:02 GMT

Closed Task: f [30392]

Miiitch — Wed, 23 Mar 2011 11:12:43 GMT

<
Comments:

Created Issue: f [30392]

Miiitch — Tue, 22 Mar 2011 21:01:10 GMT

Commented Issue: Fissum display deleted/detached collections [30092]

Miiitch — Tue, 15 Feb 2011 09:48:15 GMT

Our TFS 2010 server contains some collections, and some of them has been detached or deleted, but Fissum show them anyway (as Offline). Apparently, Fissum relay on registry entries to get TFS collection list. I look quickly in your code and see no call to ITeamProjectCollectionService (which is the only way I know to get the collection list of a TfsConfigurationServer). Perhaps you could relay on such interfaces/class instead of reading cache data in registry, or check TFS to verify such collection exist.

By the way, your tool is very usefull for "light" computer like my notebook. Thanks you !
Comments: ** Comment from web user: Miiitch **

Hello,

I see your point. Fissum collects the project collections from the Team Explorer configuration. This is a design choice. I would like to have in fissum the same projects collection that are already configured in the Team Explorer. I keep your idea to make Fissum aware of the deletion of a team project collection.

Regards,

Michel

Created Issue: Fissum display deleted/detached collections [30092]

Fernand423 — Tue, 01 Feb 2011 17:12:54 GMT

Our TFS 2010 server contains some collections, and some of them has been detached or deleted, but Fissum show them anyway (as Offline). I wonder how you access to the collection list. I look quickly in your code and see no call to the ITeamProjectCollectionService which is the only way I know to get the collection list of a TfsConfigurationServer. I would like to know how you get the collections list, and whatever the way, perhaps you should relay on ITeamProjectCollectionService instead.

Closed Issue: Doesn't show updated items correctly [29014]

Miiitch — Tue, 25 Jan 2011 21:28:25 GMT

I have noticed that sometimes a work item that was updated by a colleague is not updated when I look at it in fissum. It seems like an old version is being cached.

I'm using Fissum version 0.8.0.26648
Team System 2008

Closed Issue: Feature, usability: CTRL + S to save current edited workitem [14700]

Miiitch — Tue, 25 Jan 2011 21:28:13 GMT

Now I have to go to tool strip to save...

Closed Issue: Tray icon: make the colour change more pronounced/obvious when connecting to server(s) [15632]

Miiitch — Tue, 25 Jan 2011 21:27:37 GMT

I love that the Fissum tray icon changes from "greyed out" to "colour" and back as a way to indicate that it's trying to connect to configured servers. This is a very elegant and low-interrupt way to provide feedback to the user.

However, I have found over the last few days that the colour change is very subtle, and I've had to concentrate for a couple or three seconds to verify whether the icon is changing colour (i.e. connections are still being negotiated), or is just in "colour" mode (i.e. all connections are made). If the colour change was more obvious, I wouldn't have to concentrate very hard - a quick glance should be all that's required to verify whether it's connected or not.

Recommendation:
- Darken the "greyed out" colour scheme to be a darker set of whites, greys and blacks. Especially, I recommend making the mostly while background somewhere between 20-50% grey. The biggest problem so far with knowing "is it changing or not?" is that the contrast between colour and "grey" is mostly lost when at least half of the icon doesn't change colour at all between states.
- Darken the colours used in the "connected" state to make them more visible (especially next to all the other icons that have more contrast. On an LCD screen (especially on most laptops), the contrast from white to the chosen blue, green & red is not nearly enough to "stand out" as obviously coloured (at least, not at a glance). I've enclosed a screenshot of my "system tray" (notification area) to hopefully illustrate the relatively small contrast between the colours in the Fissum icon AS COMPARED TO the other icons in the tray. [If you're using a desktop screen, you still won't see how faint the colours are like on my screen, but at least you'll see how much more contrast there is relative to the rest of the icons.]

Closed Issue: Unhandled exception: TF30063: You are not authorized to access tfs02.codeplex.com [15602]

Miiitch — Tue, 25 Jan 2011 21:27:26 GMT

I just restarted Fissum after submitting a bunch of new Work Items, so that I could update one of those new items.

I tried to open one of the new Work Items, and it threw this unhandled exception.

Repro steps:
1. Create new Work Item using Fissum to a Codeplex project on TFS02.
2. Exit Fissum, restart Fissum client, wait for the balloon messages (logging into multiple TFS servers on codeplex) to finish. [Note: I'm not sure if they successfully authenticated or not, but I assume they did because I was able to view query results in the next step.]
3. Right-click Fissum, choose the project where the new WI's were added, choose My Work Items, then choose one of the new WI's.
4. Wait a few seconds, and then see the unhandled exception.

Environment: XPSP2, .NETFW 3.5, corporate network (behind a proxy that is configured via IE scripts), Fissum v0.6 Alpha.

Stack trace:

Closed Issue: System Tray Menu Splits Apart with Dual Monitors [12171]

Miiitch — Tue, 25 Jan 2011 21:27:13 GMT

On a dual monitor setup the Fissum tray menu split apart when you access the submenu of a TFS project (as shown in the attached screenshot). It would be great if the submenu stayed on the same monitor, either appearing to the right (thus covering up a portion of the main menu) or to the left of the main menu. Thanks!

Commented Issue: Add custom credentials authentication option for 1.0 [30039]

Miiitch — Tue, 25 Jan 2011 21:21:43 GMT

Hi,
the new Version is really great. One thing I'm really missing is to connect to a tfs server with custom credentials.
Would be fine to have an option/or tfs-authentication pop-up window to use different authentication options.
With this option it would be able to use fissum to connect to tfs which is not in the same domain (eg: customer).
Br, Daniel
Comments: ** Comment from web user: Miiitch **

I see what you mean, you can already do that: go to "Control Panel\User Accounts\User Accounts" then "Manage your credential" and enter your login/password for your tfs server URL. And this works also for Visual Studio.

Michel