Home > MOSS 2007 > Update:Features Project in CodePlex

Update:Features Project in CodePlex

I just uploaded another feature to our CodePlex project called Global Web.Config Feature. It is basically a feature that gives you the ability to add some of the most requested modifications such as connectionstring, appsettings , membership and providers to the Web.config files of all Web apps across the farm. The feature is scoped at farm level , but nothing stops you to change its scope to “Web Application” with some slight modifications in FeatureActivated and FeatureDeactivating event handlers. I have tested this feature for both WSS and MOSS and it should work just fine. That’s why I decided to use SPWebConfigModificationType.EnsureSection for the parent nodes instead of SPWebConfigModificationType.EnsureChildNode. If you find any issues or if you have any suggestions please let us know here.

I will be working with Scot Hillier (Project Coordinator and Developer) and other project members to clean up some of the already deployed features and incorporate some of your requests logged in the issue tracker , specially for AJAX Config and Debug Config features .Stay tunned!

You can find the complete code and solution files for this project in the CodePlex project. In the meantime , you can have a look at my post here about some of the SPWebConfigModification’s limitations.

Update (13/April/2008 ): Ajax.Config Feature is cleaned up.
Update (13/April/2008 ): 3.5 Cinfig Feature is now part of the project. This Feature makes all the Web.config modifications to support 3.5 framework so you can can easily deploy the wonderful BluePrint demo.

Categories: MOSS 2007 Tags:
  1. TJ
    September 1st, 2008 at 08:50 | #1

    After the feature “.Net 3.5 Configuration” is activated and I try accessing a web service e.g. lists.asmx I get a

    “You are not authorized to biew this page”

    Deactive the feature and all is well again. You know the cause? How can this be avoided? Thanks.

  2. TJ
    September 1st, 2008 at 09:01 | #2

    Please see Web.Config after activation

    Removing the last fixes the issue. Is this an error in the feature? Why is it removing the vers after adding them? Surely this shouldn’t be happening?

  3. Reza Alirezaei
    September 10th, 2008 at 10:30 | #3

    Renaud is updating the feature. I Will update you here once it is up there again. Thanks

  4. Sumit Kanchan
    May 1st, 2011 at 13:12 | #4

    As your post says that
    https://blogs.devhorizon.com/reza/?p=459 point 6

    “some modification types and in a farm environment the following code won’t propagate your changes across the farm
    But in my case reverse happens this works fine but another entry fails to change all the config on all the servers only some of the configs were changed.
    Can you give some focus on it?????

You must be logged in to post a comment.