ConfigurationProxy inconsistent solution package namespace prefix


This defect is inherited from the original Microsoft version of the SharePoint Guidance Library 2010 source code.

1) The ConfigurationProxy solution package is not named with its namespace prefix Microsoft.Practices.SharePoint.Common but it should be per Microsoft recommendations for naming and established conventions

However, when it is renamed appropriately, then it is no longer possible to package the solution as the overall path length of some intermediate files exceed the maximum permitted in Windows:
The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. C:\SPG\Source\SharePoint 2010\Microsoft.Practices.SharePoint.Common.Configuration.ConfigurationProxy\Features\ConfigProxyFeature\ConfigProxyFeature.feature Microsoft.Practices.SharePoint.Common.Configuration.ConfigurationProxy

Which brings to light a second issue

2) The ConfigurationProxy project file name and folder name include the term "Configuration" in the fully qualified name, whereas the LoggerProxy project does not include the corresponding term "Logger".


Removing the (somewhat) redundant term "Configuration" from both the ConfigurationProxy project file name and folder name resolves the path length issue in (1).
Closed Mar 24, 2014 at 1:55 AM by johnmcalvert


wrote Mar 24, 2014 at 1:55 AM

Resolved with changeset 107401.

wrote Mar 27, 2014 at 1:37 AM

Associated with changeset 107478.

wrote Mar 27, 2014 at 10:11 AM