SharePoint

copy/paste the script in Content Editor WebPart in SharePoint 2010 . Remove the html tag and body tag in Cotent Editor WebPart

Publish it manually from Central Administration it will Overwrite the previous version of .xsn to Latest

‘Connect to outlook’ Synchronize SharePoint content with Outlook: http://office.microsoft.com/en-us/sharepoint-online-small-business-help/synchronize-sharepoint-content-with-outlook-HA101964720.aspx Overview of Microsoft Windows SharePoint Services and Outlook 2007: http://office.microsoft.com/en-us/outlook-help/overview-of-microsoft-windows-sharepoint-services-and-outlook-2007-HA010083247.aspx?CTT=1

www.sharepointstop.blogspot.com

www.sharepointstop.blogspot.com

www.sharepointstop.blogspot.com

Reference: www.sharepointstop.blogspot.com

Install the SharePoint Server and VS on the same machine. Then start VS und create a SharePoint project. :) ------------------------------ Author of Primary ROleplaying SysTem How do I take my coffee? Black as midnight on a moonless night. War doesn't determine who's right. War determines who's left.

Hello I'm new with Sharepoint, so I may be wrong. I would define a Workflow setting a value every time a document will be changes. This value could be stored for example in a server-file. So your WebPart hasn't to go through all lists and documents - it wil read the value which identifies the newest document. Hope this will help :) ------------------------------ Author of Primary ROleplaying SysTem How do I take my coffee? Black as midnight on a moonless night. War doesn't determine who's right. War determines who's left.

I don't have the time now to research this, but I believe it's possible. I would look at some site workflows and how to associate them via code with the resources you are looking for, probably fed from an xml file or something. In other words, you may not be able to follow traditional methods, but I am sure that there is a component useful from an api perspective that can do this. You may also look for a third party component at codeplex or for a fee from the Bamboo Solutions people or something like that. Keep at it and I think you find a way. This also sounds like a common need, so you may discover a market for this as well. ;)

I am up against a couple of deadlines for grad school and work at the same time. Here is what I can tell you fast. What you want is possible. I would setup the coding research tasks as follows: code doc lib url as property of web part (this gives you a flexibility for where doc lib can be--not hard coded). Rt click on doc in lib get url directly to item in library. http://zimmergren.net/technical/how-to-custom-web-part-properties-toolpart[^] Next read and write to xml file in doc library. I gave you the read part. The write part is here: Updating list item in document library[^]Of course we would point to Codeproject where possible.:cool:

This is for Office365, but the Windows settings revealed should give you a good primer for what you are trying to grasp here.Win SSO Sharepoint/Office365 :doh:

Format your code snippets when posting don't post to multiple forums. You have already asked in Q&A Failure is not an option; it's the default selection.

I didn't know you could set properties on a feature via powershell. That is pretty cool. I think we are going to just have to agree to disagree with the coding it within VS then recreate it in PowerShell. If you are experience with PowerShell, then yes, simply create it only in PowerShell. However, if you are new to PowerShell and dont know the syntax, then do it in VS first, then convert it to PowerShell. An inexperience PowerShell developer could easily learn how to convert simple C# syntax into PowerShell. In my experience, when I was trying to configure search for a SharePoint environment, I wanted to use PowerShell. I started off doing it in PowerShell and I could not figure out how to initially code it without any intellisense. Yes PowerGui does offer some intellisense but not for the deep search configurations. Therefore, I created it in VS first. It was even difficult to do within VS. I finally got it to work inside VS and then moved it to a Powershell script. Chris

http://sharepointgeorge.com/2010/installing-sharepoint-2010-privilege-service-accounts/[^] Failure is not an option; it's the default selection.

we can create a workflow through sharepopint designer or custom visual studio workflow.