Community Server Stuff

Source code checked in

interscape — Fri, 22 Feb 2008 00:41:29 GMT

Initial copy of CSStuff 2007.1 project to branch off for CS2008 support.

Source code checked in

interscape — Thu, 21 Feb 2008 23:16:53 GMT

Changes to prepare the source control to handle separate codebases for CS2007.1 and CS2008

NEW POST: Works with 2007.1 ?

Peaboy — Fri, 26 Oct 2007 04:10:14 GMT

I just wanted to verify that this is working with 2007.1, it specifically calls out 2007 SP2.

Thanks,
-p

Source code checked in

interscape — Mon, 22 Oct 2007 22:26:30 GMT

Checking in a bunch of new controls and bug fixes in anticipation of releasing CSStuff 2007.1

NEW POST: Version 2.0 Questions

Dbruyere — Sat, 06 Oct 2007 23:17:15 GMT

I noticed some new forms in the latest upload. Is there any documentation available that shows how to utilize CommunityServerStuff? I'm still trying to get the birthday control to be added to the user registration.

Source code checked in

interscape — Thu, 04 Oct 2007 23:09:18 GMT

Lots of changes for CSStuff 2.0. We've got new controls in there, plus fixes for existing controls. Enjoy.

Source code checked in

interscape — Mon, 24 Sep 2007 08:33:56 GMT

Changes for v2... not quite finished yet but pretty close.

NEW POST: UserProfileSubform

Dbruyere — Fri, 17 Aug 2007 18:23:45 GMT

Has anybody been able to get the Gender control to work? I'm trying to ad it to the registration via the UserProfileSubform and it doesn't work.

NEW POST: Open for Developers?

interscape — Tue, 03 Jul 2007 22:54:39 GMT

Of course, David! Welcome to the group :).

NEW POST: Open for Developers?

DavidVoss — Sat, 30 Jun 2007 04:51:16 GMT

I saw Keyvan's post about Extras & Stuff merging. I was wondering if there's room for another developer here. Now that I'm getting caught back up with CS and working with Chameleon controls (which are totally awesome!) I'm sure I'll have some extra stuff as well.

NEW POST: Namespace & Assembly Naming

DavidVoss — Sat, 30 Jun 2007 03:50:43 GMT

Looks good. The only suggestion I have for namespaces is to make it HttpHandlers vs. Handlers to be consistent.

If I may make a suggestion for the physical structure, organize the controls folder similar to how CS is organized. For example, put all the Forms controls into the Forms folder. It'll help keep it organized and make it quicker to find the type of control you're looking for.

NEW POST: Release Numbers

thoemmi — Fri, 29 Jun 2007 19:58:21 GMT

For my (yet) private CS project my build script uses the same version scheme as Telligent: the major and minor version are the same as CS (3.0), the buildnumber is 2MMdd, and the release number is incremented automatically. However, if we plan to make several releases for the same CS version, we might want to change that.

NEW POST: Namespace & Assembly Naming

thoemmi — Fri, 29 Jun 2007 19:49:59 GMT

Yeah, CSModules is a mess as regards the multiple projects. Having a single project makes both debugging and deployment much easier.

The namespaces make sense. I´m fine with them.

Source code checked in

Keyvan — Fri, 29 Jun 2007 15:21:50 GMT

Made some teaks and tried to check in the LastYearThisTime control but that simple code didn't work! Will check it out tomorrow! I have to find how WeblogThreadQuery filters posts by day.

Source code checked in

Keyvan — Fri, 29 Jun 2007 08:17:39 GMT

Readded SP2 assemblies to project. They couldn't be loaded on my side. Handlers/SiteAtomFeed.cs and Handlers.SiteRssFeed.cs can't be loaded here as well.

Source code checked in

interscape — Thu, 28 Jun 2007 10:22:35 GMT

Changes to the codebase to remove "RobertMcLaws" from the assembly name and namespaces.

Project License Changed

Thu, 28 Jun 2007 07:10:15 GMT

Copyright (c) 2006-2007, Robert McLaws, Keyvan Nayyeri, and Thomas Freudenberg All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of CommunityServerStuff nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

NEW POST: Change the License to BSD?

interscape — Thu, 28 Jun 2007 06:43:15 GMT

Works for me, I'll change it.

NEW POST: Release Numbers

Keyvan — Thu, 28 Jun 2007 04:54:59 GMT

Like namespace and assembly naming, we also need a release version naming convention for the project.

Should we use codenames for each release or follow a constant version numbering method?

NEW POST: Merging CSModues Project with CSStuff?

Keyvan — Thu, 28 Jun 2007 04:51:46 GMT

You know that we have another project named CSModules Repository which has had three releases so far and some CS MVPs have worked on it.

We can suggest to merge that project with CSStuff as well but before sending this suggestion to its project members, I want to ask from you: do you like to have that project merged with CSStuff here?