wicreator Forum Rss Feed

New Post: Issues with WICreator - Information Required

Piero95 — Tue, 17 Nov 2009 09:18:40 GMT

Hi Loïc and thank you for your feedback,

I try to fix the situation today.

Kind regards.

New Post: Issues with WICreator - Information Required

loicbaumann — Tue, 17 Nov 2009 06:15:19 GMT

Hi,

You could make it work on another port than 8080, so 8083 should be fine.

In the TFSSetting you have to give the url of the TFS server, so it's like <TFSSettings url="mytfs:8080"/> and not the one of the WICreator WebApp.

By default WICreator creates a WepApp during the Installation in the Application Pool you choose, if you chose the one of Team Foundation Server it created the files in "Programm Files\..". Maybe you have another instance now because you manually created one for the port 8083 and it would typically be in Inetpub.

If you use the 8083 port, look in IIS where the files are stored (but I belive it's in Inetpub) and use the NetworkModels.xml accordingly.

I had reports where it's not easy to administrate WICreator when you don't have acces to the server, in fact I didn't design it to be administrated outside the server. You can succeed if you have the directory where the NetworkModels.xml is shared, but it's not the best way.

One last thing: if the NetworkModels.xml is on a different port than 8080, I belive you would have to registrate the TFS Alert manually to get the Work Item workflow feature working.

New Post: Issues with WICreator - Information Required

Piero95 — Mon, 16 Nov 2009 17:37:41 GMT

Hi,

I have an issue after modifying "NetworkModels.xml" file; I get a 404 error, I have some questions to try and understand what the problem is.

- I had some problems making WICreator running on port 8080 on my server, alternativelly I made it work on port 8083, is there any trouble with it ?

- If the above point is not a problem, wich URL has to be entered here in "NetworkModels.xml" : <TFSSettings url=" ? " /> is it the URL to access WICreator(through 8083) or the server through 8080 ?

- There are two "NetworkModels.xml" files, one in "Programm Files\..." the other one is in "C:\Inetpub\WINetwork" wich is the one that have to be upgraded ?

It is difficult for me to make those tests because I don't have access to the server, if someone could help me on these points...

Thanks in advance to everyone;

Regards.

New Post: Link to parent / childs

LoicBaumann — Sun, 20 Jul 2008 20:27:35 GMT

Hi all,

The very first version of the WICreator was using Work Items links, but I had to give up for many reasons that you'll find in this blog post.
I whish I could stay with Work Item Links as it fits better in TFS (Reports, WIQL, and so on...) but unfortunately, to handle a large scale hierarchy (which was what I was - and did- aiming to) it was just not possible.

For the integration within VSTS, I'd like to have few days to replace the whole GUI of WICreator and make a VSPackage instead. Deployment would be less easy, but I undestand all the advantages it would bring to the end user.

Regards,
Loïc

TSchissler wrote:
Hi DmytroL,

thanks for your response. In the meanwhile we have developt a tool for hierarchical workitems on our own. If you want, you can download a trail here: http://www.artiso.com/register_click.aspx (sorry page is currently only available in German, but the tool comes with a English frontend).

DmytroL wrote:
I'd add that, instead of having custom ID fields to establish and track the hierarchy, the tool could use links between work items instead. It would just require an assumption that, say, Scenario is always at the top level of the hierarchy, Task and Bug are always at the 2nd level etc.

bow wrote:
Currently it is only possible to see the relation between the work items in the WI Creator. It would be fine to have also a link between the work items. This could be used also within the Visual Studio.

New Post: Link to parent / childs

TSchissler — Thu, 17 Jul 2008 13:53:45 GMT

Hi DmytroL,

thanks for your response. In the meanwhile we have developt a tool for hierarchical workitems on our own. If you want, you can download a trail here: http://www.artiso.com/register_click.aspx (sorry page is currently only available in German, but the tool comes with a English frontend).

New Post: Link to parent / childs

DmytroL — Thu, 17 Jul 2008 11:13:15 GMT

I'd add that, instead of having custom ID fields to establish and track the hierarchy, the tool could use links between work items instead. It would just require an assumption that, say, Scenario is always at the top level of the hierarchy, Task and Bug are always at the 2nd level etc.

NEW POST: Missing CegTFSHelpers Project

intrepid — Wed, 14 May 2008 19:55:48 GMT

Thanks a lot Loïc.

Also a note to anyone else reading this discussion, to get the code for the 'Aga.Controls' reference, go to:
http://sourceforge.net/projects/treeviewadv/

-Manish

NEW POST: Missing CegTFSHelpers Project

LoicBaumann — Wed, 14 May 2008 07:35:46 GMT

I added it, update the solution and projects dependencies.
You should compile everything now. :)

Regards,
Loïc

intrepid wrote:
Hi,

I am trying to build the solution but the 'CegTFSHelpers' project is missing. Is the source available for it?

NEW POST: Missing CegTFSHelpers Project

intrepid — Wed, 14 May 2008 00:17:07 GMT

Hi,

I am trying to build the solution but the 'CegTFSHelpers' project is missing. Is the source available for it?

NEW POST: How it works with Conchango Scrum v2.0?

LoicBaumann — Mon, 28 Apr 2008 16:38:05 GMT

Yes it works with any kinds of Process Template.
It's up to you to design how you want to use the features of WICreator with a process you're using in a Team Project.

Regards,
Loïc

ralcalde wrote:
I would like to installed to simplify backlog item... can it be used without any problem?

NEW POST: How it works with Conchango Scrum v2.0?

ralcalde — Fri, 25 Apr 2008 16:48:16 GMT

I would like to installed to simplify backlog item... can it be used without any problem?

NEW POST: Does WICreator work against Codeplex?

LoicBaumann — Tue, 11 Mar 2008 07:13:10 GMT

I made the test, you can't modify the WIT definition on Codeplex.

Loïc

NEW POST: Does WICreator work against Codeplex?

LoicBaumann — Mon, 10 Mar 2008 22:06:02 GMT

Hi,

In the release currently under development I check if the Work Item Types of the selected Team Project have the fields required to handle hierarchy. If it's not the case, I propose to modify the template definition to add them. (which is a big time saver for setting up the whole solution...)
In theory, if you have the rights to modify a Work Item Type, it should work (if you configure the XML file correctly and install the web service on a separate server).
But I doubt that the Codeplex team allow you to modify the definition of the proposed Work Items...
I'll try to make the test tomorrow, but still, hopes are slim.

Regards,
Loïc

NEW POST: Does WICreator work against Codeplex?

MikeSL — Sat, 08 Mar 2008 23:49:41 GMT

UPDATE: nevermind, I finished reading the "About and setup.doc" and realized that:

there's no client that I can run without installing this on a server
the client wouldn't work anyway unless the Codeplex team installed the web service (which I'm guessing they haven't)

Thanks anyway!

Loic, great-looking tool you have here. I found it when I went looking for a client-server app that would allow me to create and update Work Items on my Codeplex projects.

When I started reading the "About and setup.doc" that's included with the v1.3 release, I was scared by the fact that within the first page, you're already talking about "Customization of the Work Item Types". I don't know whether Codeplex even lets us customize our projects hosted on their servers, and my first thought is "What if this application tries to make changes to the server, but fails, and causes my project to get corrupted?"

I realize this is probably not possible - if the Codeplex team has blocked our ability to make customizations, then a tool like this probably wouldn't have the permissions to do any harm to the server. However, it would be very reassuring if the installation document (or the WICreator project wiki) made it clear to new users like me:

Whether this tool works at all with Codeplex?
If so, are there any special steps to make sure it "plays nice" with Codeplex?
What limitations might exist when using this tool with Codeplex?

I'll try this myself and report any unusual results, but I'd like to request that you update your documentation, so that future "new users" like me can use WICreator + Codeplex worry-free! :)

NEW POST: Rebuild WICreator App

LoicBaumann — Thu, 14 Feb 2008 20:55:51 GMT

Ok, I think you're right, the sources uploaded on Codeplex are certainly not up to date. I remember now it was hard for me to do it because I already had a newer version in local and didn't want to share it (too experimental).

I had to stop the development of WICreator for many months, too many other things to do. But lucky you, I started again two days ago. :)

I worked on a new feature that took time to stabilize, we're using it in production in my company for several months now, so that's why I decided a couple of days ago to make a new release of WICreator.

The new feature I'm talking about is the ability to merge branches using Work Items, it's a biiiiig time saver (and a cool way to handle the development of multiple versions of your project at the same time).
I also didn't want to release this feature because of a bug in TFS 2005 that made it damn slooow, but now with TFS 2008 it's like we are no longer waiting 10 min (that's right), but only 20 seconds ! So I feel I can release the feature as it's really usable for production.
Post me a private message with your email, I'll send you the actual source code!

Well, time to blog that! :)
Too many months I didn't blog...geez...time goes too fast...

Loïc

NEW POST: Rebuild WICreator App

kronwodc — Thu, 14 Feb 2008 12:32:59 GMT

LoicBaumann wrote:

You have to modify the "NetworkModels.xml" file stored in the WINetwork web application to fit your needs.
You'll find more information in the "WINetwork & WICreator - About and setup.doc" document (found in each release of the project, but not SCM Versionned).
The XML file is also well documented to know how to tweak it.

Regards,
Loïc

Hello Loïc
i already modified the NetworkModels.xml (See Screen 1 with custom Icons and so on). And with the downloaded binaries from Codeplex all works really great !
But i can't compile a new Version of the WI Creator that works properly. Screen 2 shows the rebuilt app accessing the same NetworkModels.xml on the same TFS like in Screen 1.
I want to rebuild the WICreator project against the TFS 2008 DLLs, but it seems to me that the code from version control doesn't use the NetworkModels.xml when clicking on the Actions button.
Do you have more recent sources than available on CodePlex?

Thanks for your quick reply, and of course for WINetwork :-)
Wolfgang

NEW POST: Rebuild WICreator App

LoicBaumann — Thu, 14 Feb 2008 11:43:33 GMT

kronwodc wrote:
Hello,
i've downloaded the latest source code from WICreator (Changeset 3320) and tried to rebuild it with MS Visual Studio 2005.
This was successful and i can start the newly built WICreator, but when i click on the "Actions" button i can only create a Change Request or a Bug althogh my TFS project does not have these work item types.
With the binaries that i've download from CodePlex everything works fine. There i can create the right work item types which in my case are a Requirement or a Task.
Custom icons for work items don't work either in the rebuilt WICreator.

I uploaded two screenshot where you can see the described problem:
Screen 1: downloaded binaries http://img337.imageshack.us/my.php?image=origwicreatormx4.jpg
Screen 2: rebuilt binarieshttp://img179.imageshack.us/my.php?image=rebuiltwicreatordb5.jpg

Can you help me ? What am i doing wrong ? Did i download the wrong source code ?

Wolfgang

You have to modify the "NetworkModels.xml" file stored in the WINetwork web application to fit your needs.
You'll find more information in the "WINetwork & WICreator - About and setup.doc" document (found in each release of the project, but not SCM Versionned).
The XML file is also well documented to know how to tweak it.

Regards,
Loïc

NEW POST: Rebuild WICreator App

kronwodc — Thu, 14 Feb 2008 10:54:18 GMT

Hello,
i've downloaded the latest source code from WICreator (Changeset 3320) and tried to rebuild it with MS Visual Studio 2005.
This was successful and i can start the newly built WICreator, but when i click on the "Actions" button i can only create a Change Request or a Bug althogh my TFS project does not have these work item types.
With the binaries that i've download from CodePlex everything works fine. There i can create the right work item types which in my case are a Requirement or a Task.
Custom icons for work items don't work either in the rebuilt WICreator.

I uploaded two screenshot where you can see the described problem:
Screen 1: downloaded binaries http://img337.imageshack.us/my.php?image=origwicreatormx4.jpg
Screen 2: rebuilt binarieshttp://img179.imageshack.us/my.php?image=rebuiltwicreatordb5.jpg

Can you help me ? What am i doing wrong ? Did i download the wrong source code ?

Wolfgang

NEW POST: VSTS2008 support

LoicBaumann — Mon, 03 Dec 2007 12:33:53 GMT

I'll say you can use the current release of the WICreator with a TFS 2008.

Both WICreator and WINetwork will work fine. I didn't test the later, but if the alert registration didn't change, I think you'll be just fine !

Loïc

NEW POST: VSTS2008 support

LoicBaumann — Fri, 23 Nov 2007 16:22:31 GMT

I don't know exactly, I've been quite busy past months, so I couldn't manage to test it.

But I'll try this week end and let you know as soon I as can.

Loïc

tscott wrote:
Do you plan for a VSTS2008 release?
has anyone tested WICreator with the 2008 release?
Is the only thing you need to do to recompile with the new 2008 bits, or will there be any migration work to be done?