SPConfigStore Release Rss Feed

Updated Release: Release 2.1.0.2 (Sep 03, 2009)

chrisobrien — Thu, 03 Sep 2009 23:17:49 GMT

Changed internal field names back to not contain spaces - caused problem under some circumstances (an issue reported by Waldek when Config Store used with certain provisioning code)
Changed ApplyWebConfigModifications Feature property back to True, since seems most installations use single site collection mode
Tidied schema.xml based on recommendations made in http://mo.notono.us/2009/02/moss-dreaded-schemaxml.html

Released: Release 2.1.0.2 (Sep 03, 2009)

Thu, 03 Sep 2009 23:17:49 GMT

Changed internal field names back to not contain spaces - caused problem under some circumstances (an issue reported by Waldek when Config Store used with certain provisioning code)
Changed ApplyWebConfigModifications Feature property back to True, since seems most installations use single site collection mode
Tidied schema.xml based on recommendations made in http://mo.notono.us/2009/02/moss-dreaded-schemaxml.html

Updated Release: Release 2.1.0.2 (Sep 03, 2009)

chrisobrien — Thu, 03 Sep 2009 23:17:00 GMT

Changed internal field names back to not contain spaces - caused problem under some circumstances (an issue reported by Waldek when Config Store used with )
Changed ApplyWebConfigModifications Feature property back to True, since seems most installations use single site collection mode
Tidied schema.xml based on recommendations made in http://mo.notono.us/2009/02/moss-dreaded-schemaxml.html

Created Release: Release 2.1.0.2 (Sep 03, 2009)

chrisobrien — Thu, 03 Sep 2009 23:11:12 GMT

Release notes

Changed internal field names back to not contain spaces - caused problem under some circumstances (an issue reported by Waldek when Config Store used with )
Changed ApplyWebConfigModifications Feature property back to True, since seems most installations use single site collection mode
Tidied schema.xml based on recommendations made in http://mo.notono.us/2009/02/moss-dreaded-schemaxml.html

Updated Release: Release 2.1.0.1 (May 09, 2009)

chrisobrien — Sat, 09 May 2009 22:35:59 GMT

Fixes a regression bug in the previous release (2.1.0.0) which caused web config modifications NOT to be removed on Feature deactivation. This would only occur for users who made a change to the 'ApplyWebConfigModifications' Feature property before deploying the Config Store - by default, this property is set to 'False' in the packaged files.

Sidenote

When this is set to 'True', the required web.config keys get added automatically, and (following this fix) get removed automatically when the Config Store Feature is deactivated.

Sorry about that folks.

Released: Release 2.1.0.1 (May 09, 2009)

Sat, 09 May 2009 22:35:59 GMT

Created Release: Release 2.1.0.1 (May 09, 2009)

chrisobrien — Sat, 09 May 2009 22:30:17 GMT

zzzz

Updated Release: Release 2.1.0.0 (Apr 20, 2009)

chrisobrien — Mon, 20 Apr 2009 22:38:08 GMT

This release fixes an issue where under certain circumstances, entries in the list cannot be edited because only 1 field is visible on the edit form. In actual fact the fields are still there, but they can only be updated using the API which isn't very convenient!

Sidenote

I had seen this behaviour when SharePoint Content Deployment was used to deploy the list, but not under other circumstances. However, I think a change in either the October 2008 or December 2008 Cumulative Update has caused it to be more of a problem, and I had a handful of reports of this problem.

Happily just as I'd started to look for the problem, Richard Browne (no blog) found it for me (was using field display names rather than internal names in ContentTypes/FieldRefs in Feature ConfigStoreElements.xml) and sent me the fix. Kudos and many thanks Richard!

I've tested this in as many ways as I can think of (including Content Deployment), and it seems solid - I'm confident this is now fully resolved. Apologies for the inconvenience.

Released: Release 2.1.0.0 (Apr 20, 2009)

Mon, 20 Apr 2009 22:38:08 GMT

Updated Release: Release 2.1.0.0 (Apr 20, 2009)

chrisobrien — Mon, 20 Apr 2009 22:33:22 GMT

This release fixes an issue where under certain circumstances, entries in the list cannot be edited because only 1 field is visible on the edit form. In actual fact the fields are still there, but they can only be updated using the API which isn't very convenient!

Sidenote

I had seen this behaviour when SharePoint Content Deployment was used to deploy the list, but not under other circumstances. However, I think a change in either the October 2008 or December 2008 Cumulative Update has caused it to be more of a problem, and I had a handful of reports of this problem.

Happily just as I'd started to look for the problem, Richard Browne (no blog) found it for me (an issue in schema.xml) and sent me the fix. Kudos Richard!

I've tested this in as many ways as I can think of (including Content Deployment), and it seems solid - I'm confident this is now fully resolved. Apologies for the inconvenience.

Created Release: Release 2.1.0.0 (Apr 20, 2009)

chrisobrien — Mon, 20 Apr 2009 22:11:30 GMT

This release fixes an issue where under certain circumstances, entries in the list cannot be edited because only 1 field is visible on the edit form. In actual fact the fields are still there, but they can only be updated using the API which isn't very convenient!

Sidenote

I had seen this behaviour when SharePoint Content Deployment was used to deploy the list, but not under other circumstances. However, I think a change in either the October 2008 or December 2008 Cumulative Update has caused it to be more of a problem, and I had a handful of reports of this problem.

Happily just as I'd started to look for the problem, Richard Browne (no blog) found it for me (an issue in schema.xml) and sent me the fix. Kudos Richard!

I've tested this in as many ways as I can think of (including Content Deployment), and it seems solid - I'm confident this is now fully resolved. Apologies for the inconvenience.

Updated Release: Release 2.0.0.0 (Jan 20, 2009)

chrisobrien — Sun, 01 Feb 2009 19:29:13 GMT

Changes in this release (see http://www.sharepointnutsandbolts.com/2009/01/better-config-store-for-sharepoint.html for full details):

- Optional "hierarchical" configuration model similar to web.config
- Easier to use in ASPX markup (expression builder support)
- Fixed caching bug for farm environments
- Amendment to Feature to prevent web.config modifications being made on Feature activation
- 'Config value' now stored in a larger field - can store HTML/XML fragments etc.

Released: Release 2.0.0.0 (Jan 20, 2009)

Sun, 01 Feb 2009 19:29:13 GMT

Created Release: Release 2.0.0.0 (Jan 20, 2009)

chrisobrien — Tue, 20 Jan 2009 14:57:01 GMT

Released: Release 2.0.0.0 (Jan 20, 2009)

Tue, 20 Jan 2009 14:57:01 GMT

CREATED RELEASE: Release 1.0.1.0 (May 13, 2008)

Tue, 13 May 2008 21:28:18 GMT

There was an issue with the packaging of release 1.0.0.0 - the wrong Feature.xml file had made it into the package (had the old assembly name), so this caused the following issues:

- entries not being added to web.config
- event handlers not being added to config store list
- error upon feature deactivation

It would be possible to resolve these things manually, but a simpler way is to download release 1.0.1.0 and re-run the install script against the new .wsp. The following should happen:

- feature should deactivate/uninstall, solution is retracted and dedeployed
- installation now is successful, event handlers added and web.config entries added (note will be duplicated if you added manually)
- list gets created again at default location, or if already present the 2 test items get added AGAIN. ** Note if using the 'ConfigTestControl' to verify the framework works, this will throw an exception stating 'more than 1 item found for that config value'. Simply delete the duplicate test items to get it working again. **

Thanks and apologies to any 1.0.0.0 users..

Chris.

CREATED RELEASE: Release 1.0.0.0 (May 11, 2008)

Sun, 11 May 2008 12:13:07 GMT

All source code/Feature files etc. are included in the zip file.

RELEASED: Release 1.0.0.0 (May 11, 2008)

Sun, 11 May 2008 12:13:07 GMT

All source code/Feature files etc. are included in the zip file.