View Complete Post
Office 2010 and SharePoint 2010 include a new set of components called Application Services. These put a rich set of tools in a developer's bag for Office automation. We'll show you how to use Office OpenXML, Word Automation Services and SharePoint to build a simple application that merges separate status reports into a single document.
Manvir Singh, Ankush Bhatia
MSDN Magazine July 2010
Subject is the question.
My requirements are to "maintain existing functionality with current version of a windows service running on Server 2003 and automating Word through COM." I.E. All the stuff that breaks when you upgrade the OS to Server 2008.
My customer has already rejected several third party alternatives as "not being accurate enough" The rendered PDF doesn't match what comes out of Word when compared with an electron microscope.
So now I'm investigating using Word Automation Services and Sharepoint 2010. Got my development server functional with Sharepoint 2010 and Visual Studio 2010. But my first attempts at creating rendering jobs is failing with an "ArgumentNullException"
in deep inside a method I'm 100.0% sure I'm NOT passing any NULL's to.
My VM is low on space so I figure I'd save time by asking for a conclusive answer before I make room / install Office.
I need to import 700 Word docs (2003 & 2007) from Windows Server 2003 into a SharePoint Server 2010 library. I only have a test server to work with right now and want to do as much pre-work before we launch the actual
My goal: When we launch the shpt server, import all docs into a library so that columns propagate with metatdata automatically.
I'm not sure what the best approach is...
Can I can open each doc and add custom properties (maybe with InfoPath) to import as metadata, then import managed metadata through the term store tool and have it associate with the manually entered custom properties? I don't fully understand
managed metadata, which might pose a problem. And before I start importing terms, I thought I should find out if I've completely misunderstood how taxonomies work.
Or I have an excel spreadsheet with info about each doc in columns that can act as metadata. I could upload this as a list then associate each doc with the list. But it seems wiser to enter the metadata into the documets.
Is it possible to update my docs in advance so that uploading goes smoothly? I have help now for data entry that I won't have later.
I have no resources to spend on tools, and have to figure out and build this&nbs
The first time a document is opened it's fine, opens in just a few seconds.
Subsequently, there is a long delay (about 20 seconds) in the "Contacting server for information..." step.
This happens to all users and all documents, each one will open fast the first time then slowly the second and subsequent times (until, we think, the app pool is recycled - there is no schedules iisreset/reboot).
This does not happen when using Office 2007.
IE6 and 7 exhibit the same behaviour.
I only found one thread for this, and it points to one either i don't have access to or that has been disabled:
My problem is that some Word documents are returning in Search Results with the first word on the page as opposed to the document title and i'm not sure where it is coming from. The document properties i can view via SP and those that i can view from within
the Word document are set correctly, so i can't figure out why Search is showing the first word in the document. This isn't happening for all Word documents, only some of them.
Any insight would be helpful!
Using word automation services, we cannot convert a doc/docx to FILTERED html, which can be done on client side using "saveas".
Is there any unexposed API through which one can achieve this using SharePointServer2010 + c# programatically.
or any alternative way to get FILTERED HTML format file from doc/docx?
I knew the way to do this as a client side application. This can be acheived simply by recording macros.