AD User Editor - Sources, Evolutions and Modifications

Print PDF
Article Index
AD User Editor
Setup
Configuration
Sources, Evolutions and Modifications
All Pages

References

I picked a lot of infos and get inspirated by some bits of source code googling the web. My most important sources of inspiration and help were:

Wishes List

  • More friendly property editor in webpart configuration (like toolpart in this webpart, or from an external list)
  • Encode connexion strings (no more clear text)
  • Make it really multilingual (cf here)
  • Code it the MVC way (at least separate presentation elements from data)
  • Add multi-valued field to properties control types (find the sharepoint one which does this task)
  • Package it with SharePoint Solution Installer

Before trying to compile something

  1. Use a server with MOSS 2007 and Visual Studio 2008 installed on it (not tested with VS2005 and WSS3 alone)
  2. Install Visual Studio Extensions for Sharepoint from here
  3. Download and install STSDEV from here
  4. Unzip the project archive and open NomineSharePointTools.sln with Visual Studio
  5. Edit DeploymentFiles/Microsoft.SharePoint.targets to make targetUrl, WssRootFilesFolder, STSADM and STSDEV match your server config.
  6. Click the menu "Generate>Config Manager" and select DebugDeploy or DebugUdate depending on what you did before.
  7. Press F5: It should compile and install (don't care if VS tells you a class can't be directly launched)
  8. You just have to activate the feature on you site collection and then add the webpart to a test page.
  9. Next, each time you'll update, the webpart will be automagically updated.

 

Conclusion

Thank you for trying my WebPart. It's my first real developement for SharePoint 2007, so feel free to send any constructive comment to help me making it even better.



Comments  

 
0 #6 Alexis 2010-03-04 15:09
Steev,
The issue is related to the xml config in the webpart:
check here for more info: http://nominesptools.codeplex.com/Thread/View.aspx?ThreadId=69492
Quote
 
 
0 #5 Steev 2010-02-18 17:17
Hello, I am having some trouble getting the WebPart to work.

I have installed it successfully and added it to a MOSS page, but I get an error.

I seem to get the same error whether I enter my DC creds or not.

The error is

"System.Collections.Generic.KeyNotFoundExce ption: The given key was not present in the dictionary. at System.ThrowHelper.ThrowKeyNotFoun dExce ption() at System.Collections.Generic.Dictionary`2.get_Item(TKey key) at NomineSharePoin tTools.ADUserEditor.findFromAccount Name(String Name) at NomineSharePoin tTools.ADUserEditor.selectUser"

Fairly noob at this so it's probably something obvious I am missing. I would appreciate any help you can give me as the WebPart is exactly what I am looking for.

Thanks.

Steev.
Quote
 
 
+1 #4 Tom J 2010-02-16 12:30
Excellent web part. See link for configuration gotchas I found. Main thing is to make the 'Edit current user only' property non-editable when modifying the web part in personal mode.
Quote
 
 
0 #3 Ivo Markov 2010-02-04 11:29
Hi, great toll but one real nice option is missing. There is no way to pass the current logged in in MOSS user's credentials to the AD. It'll be very nice to have that as setting administrator account into the WebPart configuration is not an option in most companies. Anyway, user by default can change some of his attributes in AD, and if passing his credentials automatically is possible this tool can be useful in more scenarios.
It's pretty simple to do it in WebApp, I think can be done in WebPart.
Quote
 
 
+1 #2 mlem 2010-01-07 01:12
Great tool, Alexis. Is there a way to make a field read-only?
Quote
 
 
+1 #1 pettsen 2009-12-09 09:44
Great job
Quote
 

Add comment


Security code
Refresh

Documentation:
Creative Commons License

Source Code:
GPL v3

If you like my work: