fissum Forum Rss Feed

New Post: How do you undo changes to a workitem?

miiitch — Mon, 07 Sep 2009 16:37:28 GMT

Hi,

This is a known bug for me. I'm working on the refresh scenario and undo changes is one of the task: undo is just a refresh of the server version. The refresh scenario is not that simple because I have also to refresh queries area, iteration.....

Regards,

Michel.

New Post: How do you undo changes to a workitem?

paul55br — Thu, 27 Aug 2009 17:38:10 GMT

Hi,

I had made a change to a workitem, then I hit the close button, but it didn't delete the changes I made to the workitem.
I didn't even hit save. Is there a way undo the changes a person made to the workitem?

Thanks,

Paulo

New Post: Goto Work Item

trmurali — Tue, 11 Aug 2009 09:03:43 GMT

Ooops I got it ... ;)

New Post: Goto Work Item

trmurali — Tue, 11 Aug 2009 08:57:54 GMT

Hello,

In fissum we have goto Workitem feature ?

Or it will come in future version.?

New Post: Which TFS client files are needed for Fissum to work?

miiitch — Thu, 23 Jul 2009 13:16:09 GMT

Hello Mike,

Fissum is built to work if the Team Explorer is installed. The main reason is I don't what to ship MS assemblies with the fissum install. When Fissum starts, Fissum search in the registry if the Team Explorer is installed and where. It must have a bug here because you should not have an exception here but a message.

If there is an untested and "at your own risk" suggestion it would be set the good registry key and put the team explorer dll as they would be if the team explorer was installed. The key is "HKLM\SOFTWARE\Microsoft\VisualStudio\9.0\InstalledProducts\Team Explorer" or "HKLM\SOFTWARE\Microsoft\VisualStudio\8.0\InstalledProducts\Team Explorer" depending your version. and the value search in "InstallDir"

Michel

New Post: Which TFS client files are needed for Fissum to work?

MIkesl — Mon, 20 Jul 2009 22:20:11 GMT

Hi Miitch, I've recently rebuilt my system and haven't had a need to install the full TFS client software suite. However, I've found that Fissum experiences an unhandled exception when I try to run it on this system where the TFS client hasn't been installed.

One of your previous discussion replies said that Fissum is built against the Team Explorer API. Is there a specific DLL that I could obtain from a TFS Client installation, copy to an appropriate location on my system, and hope to have Fissum work correctly?

Thanks for any thoughts or suggestions you may have - even if they're untested and "at your own risk".

New Post: Connect to TFS server

miiitch — Wed, 11 Mar 2009 10:07:43 GMT

In this version, the team explorer configuration is used to create the fissum context configuration. In the next version - I'm working on it to release it soon - I split the configuration to target web scenario:

* Fissum application use a part of the team explorer configuration

* Fissum core is independant and need a configuration structure (you can save it in xaml format) so it can be used withou any interaction with an another tool configuration which is generaly the case when fissum core is running in a service account.

Michel

New Post: Connect to TFS server

syedshoeb — Mon, 09 Mar 2009 16:25:09 GMT

Hi Miitch,

I am able to pass the credentials and extract the registered server. I created a sample web application. Unfortunately I did not get any registered servers when I deploy application (I am passing credentials hard coded at the moment).

Any suggestions?

Thanks
Shoeb

New Post: Connect to TFS server

syedshoeb — Mon, 09 Mar 2009 14:20:07 GMT

Hi Miitch,

Can you please elaborate how to connect to TFS server. I created a class with function which returns System.Net.NetworkCredentials. Fissum.TeamSystem.TeamFoundationServer.GetCustomCredentialsDelegate reference to this function. I am getting null into delegate. Is this the right way to use Fissum?

Thanks
Shoeb

New Post: Fissum LINQ code generation tool

syedshoeb — Tue, 02 Dec 2008 21:42:46 GMT

Many thanks for your quick response and explaination. I am very excited about Fissum APIs and looking forward to have deep dive.

Many Thanks
Shoeb

New Post: Fissum LINQ code generation tool

Miiitch — Tue, 02 Dec 2008 20:59:09 GMT

Thanks for your support :)

var q = (from wi in project.Get<Fissum.Model.Codeplex.WorkItem>()
        where wi.CodePlexWorkItemType == "Feature"
        orderby wi.CodePlexUserVotes descending
        select wi
        ).ToList();

Get<>() is an extension method and Fissum.Model.Codeplex is a generated workitem model from the process template of Codeplex.

Does this peace of code help you?

For the next version of Fissum I'm working on a "real" demo application, not just a console one.

Michel

New Post: Fissum LINQ code generation tool

syedshoeb — Tue, 02 Dec 2008 19:54:33 GMT

Please provide one sample implementation using Fissum libraries. I was trying to create a LINQ query as per the instructions in blog, but those are very high level and doesn't mention some of the object like "project". I was trying TeamFoundation client Project type as well as Fissum project type, but nowhere I can get the Get<>() implementation.

Sample would be of great help.

New Post: Fissum LINQ code generation tool

syedshoeb — Tue, 02 Dec 2008 18:38:44 GMT

It worked, excellent work Miiitch. You Rock.

Thanks for wonderful tool and set of utility

New Post: Fissum LINQ code generation tool

Miiitch — Mon, 01 Dec 2008 22:12:49 GMT

The tool is called ModelBuilder in the Fissum install directory. There is a bug in the current version: the help file is not returned. This is fixed in the next version:
Command line arguments:
To show this help: -h
To build a C# file: -model modelfile.wimd -code cs -output file.cs
To build a VB.Net file: -model modelfile.wimd -code vb -output file.vb
To build a file from the model file: mymodelName.wind -> mymodelname.(cs|vb), just remove the '-output ...' part
To build a mymodelname.Designer.(cs|vb): add '-designer' to the command line

Michel

New Post: Fissum LINQ code generation tool

syedshoeb — Mon, 01 Dec 2008 18:18:07 GMT

In the blog it is mentioned that you can generate the code using code generation tool which uses CodeDom API. I was trying to figure out this tool but no luck.

Anyone have any idea?

New Post: How easy would it be to add a different back-end repository?

Miiitch — Mon, 04 Aug 2008 15:33:39 GMT

Hello Mike,

Fissum is designed only interact with a team foundation server and a team explorer. If you look at the code, you'll see that Fissum is build on top of the Team Explorer API (that's why fissum is shipped for the both version of it). You should consider working on top of the sharepoint webservices to access to your lists and produce a similar interface. It is not as complicated as it seems.

Regards.

Michel

New Post: Possible Fissum bug (and broken Work Items page on your project)

Miiitch — Mon, 04 Aug 2008 15:27:32 GMT

Hello Mike,

I made some tests with fissum to figure out how I managed to close a work item with a "c". But each time, a upper case "C" replaces it. I'll make a program to close a work item by changing the value to "close" and see what happens :)

Michel

New Post: How easy would it be to add a different back-end repository?

MikeSL — Mon, 04 Aug 2008 01:30:57 GMT

In our corporate setting I'd like to use a SharePoint 2007 (MOSS) list as a bug-tracking database. This isn't as crazy as it first sounds - there's a reasonably adequate template for such a List available in the MOSS environment - it's called "Issue Tracking" - and it supports all the kinds of fields I'd expect to have to use in a small, ad-hoc development setting:

Title
Description
Comments
Assigned To
Issue Status
Priority
Category
Due Date
Related Issues

I really love the drop-dead easy way that Fissum allows me to create and edit issues in the Codeplex environment, and I have no equivalent WinForms (or Win32) client for managing bugs that I'd track in such a SharePoint list.

I'm not asking you to code this for me, and I'm not asking if you've ever done something like this before. I guess what I'm most interested in hearing is how well you think the code for Fissum has been encapsulated - i.e. how generic the public methods and properties are, and whether it'd be reasonable to try to re-use the Fissum codebase to implement connectivity and functionality to a different kind of back-end data store? While I'd prefer to leverage the kind of work that's already gone into this, I don't want to end up spending more time rewriting, refactoring and redesigning existing code than it would take just to develop something from scratch.

This is something that I'm enthusiastic enough about (at least for now) that I'd be willing to:

perform a detailed analysis of the Fissum codebase (if you think it's worth investigating)
submit "Patches" to you that would encompass the kinds of refactoring that might be necessary (to make any public methods or properties more generic to multiple data stores)
write the code to which the public methods and properties would call, that leads to and properly interacts with the SharePoint data-access classes

What do you think? Is this something that would interest you?

New Post: Possible Fissum bug (and broken Work Items page on your project)

MikeSL — Sun, 20 Jul 2008 19:34:42 GMT

Hi Michel,

I noticed that browsing your project's Work Items page encounters an error, which appears to be the same as the error I encountered on one of my own projects.

I was able to get it resolved by submitting a request to the CodePlex Support team, who did some "magic" behind the scenes on my behalf.

Here's what they emailed me when I asked what the root cause of the problem was (where I'd wondered if my use of your Fissum tool - which kicks ass, BTW - had caused this, or if there might be a possible bug in Fissum):

In our Issue Tracker and in TFS, work item status is represented with a capital letter at the beginning of the word, so “Open,” not “open,” etc.

One or more of your work items was closed with a lower case c, which the Issue Tracker didn’t recognize – in TFS it changes automatically to title case. We have made a correction on our end so that the Issue Tracker status will no longer be case sensitive, or it will change the case as the item comes in.

In all likelihood this is not something that the Fissum developer needs to change, since it’s an uncommon issue (which is why it is not in the Issue Tracker), and we’ve fixed it for the next release.

Even if their site won't suffer from this problem in the future, I'd hate for Fissum to encountered unexpected exceptions because of a simple uppercase/lowercase issue in certain requests.

Since I'm not able to browse your Work Items page, I can't submit a bug for this, but hopefully this Discussion thread will help you determine if there are any issues in the current Fissum codebase.

Hope this helps you,
Mike

NEW POST: v0.7 when?

Miiitch — Fri, 11 Apr 2008 16:00:55 GMT

Soon! In may I think. I've almost finished to implement the new functionnalities:

Windows position and size are stored
text search in the quick go to form,
history window,
hierarchical query display in the menu,
Fissum API with LINQ to WIQL support if you want to build a tool over Fissum API with the power of LINQ to query the Work Item repository,
New Fissum start modes,
and a lot of bug fixes!

My last issue is to keep the compatibility with VS 2005 and VS 2008 for the TF Server discovery.

Michel