SharpForge Forum Rss Feed

New Post: Will SharpForge Continue?

mysticboy — Tue, 24 Mar 2009 02:03:24 GMT

i hope continue ! this is good work!

New Post: Will SharpForge Continue?

ttafet — Thu, 19 Mar 2009 12:22:02 GMT

Does this open source project still have an owner after the sale to CVSDude? Is there a community still interested in using SharpForge and continuing its development?

Any plans on using TFS?:

SharpForger — Wed, 14 Mar 2007 11:50:35 GMT

ok, since you know what you want better than me do you feel up to writing a brief spec for it?

Have a look at how we've being doing it for the main specificaiton http://svn.projxpert.com/SharpForge/trunk/Doc/development/Index.html.

We need the 2 use cases with a brief description, pre/post conditions, basic flow and any important alternate flows. Then I can look at what the best way to do the integration from the sharpforge end.

Cheers,
Scott.

Any plans on using TFS?:

Heynemann — Mon, 12 Mar 2007 12:44:35 GMT

Actually it would be nice to have an option to create the TFS Iteration. It´s rather easy to do it.

But that would be the requirements, yes.

I can help in the TFS Code, since I do a lot of TFS coding.

Let me know,
Bernardo Heynemann
Coordinator of TFS Version Tree Browser, BHAL, WorkItem Object Mapper, NMVP, Validation Everywhere, NHibernate Business Layer and NMVP Software Factory (Former MVPGen).

Any plans on using TFS?:

SharpForger — Mon, 12 Mar 2007 04:44:05 GMT

So does this sounds like the general use cases for this integration:

o) Create Release
creates an iteration with a given TFS Path
eg. TeamProjectName/0.1.0 Beta/

o) View Release
loads all work items matching that path & display titles & description

Create Release doesn't really need to create the iteration within TFS does it(is that what you meant)? It could just have the path it's associated with and then do a query on the fly and cache the results when the release is viewed.(I'm thinking KISS).

Any help is most appreciated.

Source code?:

bsimser — Sat, 10 Mar 2007 14:59:07 GMT

Great thanks, appreciate the info and keep up the excellent work!

Source code?:

SharpForger — Sat, 10 Mar 2007 08:07:23 GMT

if you have a svn client you can get the latest source from http://svn.projxpert.com/SharpForge/trunk

There hasn't been a download file with the source code for the last couple of releases but I'll make sure the next release has one. I upload the releases there, Codeplex, SourceForge and Google Code so it takes a while to put binaries and source up to all of them. The main development is going on at http://sharpforge.org/ not Codeplex

Source code?:

bsimser — Fri, 09 Mar 2007 19:35:34 GMT

Is there a source code release yet?

Any plans on using TFS?:

Heynemann — Fri, 09 Mar 2007 12:36:38 GMT

The problem here is that I must know which workitems were added to which release, you see...
I´d like to help since I know how you can do this easily... You just have to create and Iteration in TFS for each release added to the project.
Example:
Release 0.1.0 Beta
in TFS it will be an iteration of form TeamProjectName/0.1.0 Beta/

This would add a lot of value for SharpForge in my opinion. And you can always test this integration using your own CodePlex project, since it´s a TFS project.

Other than creating an iteration it would be AWESOME if the workitem titles showed in the Release notes.
Viewing WorkItems might prove trickier, since they don´t have fixed values (only a few like title and description are fixed), but you can always provide a basic view of them, just so that people can check out what went into each release.

Hope I can help you guys out.
Great project btw. Almost everything I need from a Release Management tool.
Bernardo Heynemann
Coordinator of TFS Version Tree Browser, BHAL, WorkItem Object Mapper, NMVP, Validation Everywhere, NHibernate Business Layer and MVPGen.

Any plans on using TFS?:

SharpForger — Fri, 09 Mar 2007 08:23:37 GMT

Do you just need to provide releases? You can continue to use TFS for version control and internal work tracking and use SharpForge for release management.

SharpForge can be installed without needing Subversion, it still has release management, forums and work item functionality.
This means you can create a release, upload files and distribute them to external users. They can also subscribe to the release rss feeds.
Your users can use the forums and work items to communicate back to you.

There are no plans to integrate with TFS for version control at the moment. If there was enough support and the requirements we thrashed out it could be prioritzed.

Any plans on using TFS?:

Heynemann — Mon, 05 Mar 2007 17:20:19 GMT

I´m looking badly for a CodePlex-like Release Manager for inhouse use...
Any plans on extending SharpForge to use Team Foundation Server as SCM?

Thanks,
Bernardo Heynemann

Using SharpForge under IIS:

SharpForger — Tue, 20 Feb 2007 08:38:49 GMT

Good news, SharpForge doesn't require Apache any more. To additional options are to use SvnServe or to not use Subversion at all. SvnServe is a great addition as it doesn't require apache. This has been added because of feedback from the community.

User Forum: RE: Using SharpForge under IIS

SharpForger — Fri, 29 Sep 2006 09:11:15 GMT

Unfortunately there is no support for Subversion through IIS. It would be nice not to have to to worry about the extra installation, configuration and maintanance. However, because Apache does the job very well the effort and skill required to replace it is far beyond my resources or the scope of this project. If someone was interested in taking it on as a project then I would offer every assistance I could.

User Forum: RE: Using SharpForge under IIS

troyschneringer — Wed, 27 Sep 2006 23:00:48 GMT

or more specifically not requiring Apache for subversion.

User Forum: Using SharpForge under IIS

troyschneringer — Wed, 27 Sep 2006 22:58:37 GMT

Are there any plans to be able to use SharpForge under IIS?

Developer Forum: Phase 1 Specification

SharpForger — Fri, 01 Sep 2006 11:33:57 GMT

The SharpForge specifiication for phase 1 is about 70-80% complete. http://svn.projxpert.com/SharpForge/trunk/Doc/development/Index.html The specification includes the vision, scope, actors, use cases, non functional requirements and glossary. The use cases detailed are: * Install and configure SharpForge * Create new user account * Create new project * Edit project's roles * Edit project's role members * Edit project's role permissions * Edit project's Subversion directory access permissions * View project directory Feedback, suggestions and criticisms are strongly encouraged.