I sincerely need some help here in order to evaluate whether I need to wait for the 3.0 SDK or if I can use the 2.1 SDK to make some minor alterations to my 3.0 Beta 2 installation.
I need to modify the CommunityServerForums20 API for a 3.0/2007 Beta 2 implementation I am working on. Is it safe to assume that I could alter and re-package this library and include it in my beta installation without issue? I haven't noticed too many changes from 2.0 -> 3.0 in terms of Forums.
The details of what I need/like to do:
Duplicate CreateEditPost:TemplatedWebControl with some modifications.
The new WebControl would call a new variation of AddPost - which will call a variation of ForumSqlDataProvider.
Am I right in assuming I will need to either alter the existing Forums API/library? Could I perhaps duplicate this library and call it something else, and then deploy the new (altered) library separately into my 3.0 Beta 2 installation?
Thank you!
chrisrsimons:Duplicate CreateEditPost:TemplatedWebControl with some modifications.
CreateEditPost no longer exists in 3.0 -- The functionality is implemented using the CreateEditForumPostForm control which support SubForms for extensibiilty. I would *strongly* suggest looking at the 3.0 control and implementing SubForms (in your own custom assembly) instead of creating your own control. If possible, this will cause your changes to be more easily migrated to future versions of Community Server.
Ben,
Thanks for the reply. As always your posts and separate blog are invaluable.
Now, without the SDK for 3.0 - how would I create my own custom assembly? Do I merely need to create a new project in VS 2005 and import all CS 3.0-related assemblies? SubForms looks like what I need to modify from - I will await your response. Thanks so much.
chrisrsimons:Now, without the SDK for 3.0 - how would I create my own custom assembly? Do I merely need to create a new project in VS 2005 and import all CS 3.0-related assemblies?
Yes, you can create a new class library assembly and reference any neccessary CS assemblies (for example, CommunityServer.Discusions.dll, CommunityServer.Components.dll, and CommunityServer.Controls.dll). Then you can add your custom controls (SubForms) to this assembly, deploy it to your CS installation's web/bin folder, and reference your subform controls in your new assembly.
chrisrsimons:SubForms looks like what I need to modify from - I will await your response.
Great. SubForms were designed to provide support for additional fields/logic on forms. When you create a sub-form, you just need to implement a new class that inherits from CommunityServer.Controls.WrappedSubFormBase (in the CommunityServer.Controls.dll assembly).
As a side-note.... All Chameleon/CS2007 Form controls support excluding control definitions for fields that are not necessary for your installation -- only the bare minimum fields are *required* by the base CS Forms (for example, the CreateEditForumPostForm only *requires* references to controls for the subject, body, and submit button). So, in addition to extending the control, you can override the implementation of fields that are not required by the host form by using SubForms.
You rock.
Two on me, good sir.
Copyright© 2008 Telligent Systems Inc. All rights reserved CommunityServer.com • Telligent.com