This project is read-only.
Installing the Solution on a WSS Farm:
(This may not be required now since the new release is WSS-compatible)

To make the solution installer compatible with WSS, open the setup.exe.config file and change -

<add key="Require" value="MOSS"/>


<add key="Require" value=""/>

Now run the setup.exe

Last edited Nov 20, 2009 at 6:54 AM by sarithsircar, version 2


panoone Nov 9, 2011 at 4:10 AM 
This is because fields are deployed at the farm level, irrespective of the feature scope. The DLL and web.config SafeControlEntry will be removed along with supporting files. But if the field is in use, then it will not be deleted. This behaviour is both expected and normal.

Content types, site columns and list template instances are no exception to this rule.

murki Jul 22, 2010 at 7:34 PM 
Thanks Beejai, this solved a similar problem of mine.

Beejai Jan 27, 2010 at 8:20 AM 
DeInstall Problem:
Make Sure you delete all Fields ("Cascading Drop Down List (With Filter)") from site colums before deinstalling this solution. Deinstall doesn't do it for you. If you forget, you won't be able to access any sitec olumns any more.
Instead, you might get an error like:
"The given key was not present in the dictionary .. ThrowKeyNotFoundException()"
"at System.Collections.Generic.Dictionary`2.get_Item(TKey key).."
Reinstall Solution, delete Fields, and then delete solution to fix it.
Phew, this one took me some days..