Thanks for this. I was 99% server and office was not a good idea but a few quick googles earlier didn' return mcuh.
Have a good weekend everyone! Jon -----Original Message----- From: "Patrick Steele" <[EMAIL PROTECTED]> To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Sent: 5/4/07 10:18 PM Subject: Re: [ADVANCED-DOTNET] Build RTF Document Here's a pointer: Don't do that. :) http://support.microsoft.com/default.aspx?scid=kb;en-us;257757 "All current versions of Microsoft Office were designed, tested, and configured to run as end-user products on a client workstation. They assume an interactive desktop and user profile, and do not provide the level of reentrancy or security that is necessary to meet the needs of server-side components that are designed to run unattended. Microsoft does not currently recommend, and does not support, Automation of Microsoft Office applications from any unattended, non-interactive client application or component (including ASP, DCOM, and NT Services), because Office may exhibit unstable behavior and/or deadlock when run in this environment." --- Patrick Steele http://weblogs.asp.net/psteele -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Robert Rolls Sent: Friday, May 04, 2007 8:38 PM To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: Re: [ADVANCED-DOTNET] Build RTF Document Ironically we've just written a server side Word PIA VSTO solution that uses bookmarks to identify where values need to be inserted - Literals, XPath Lookups, RTF etc. Words implementation of Bookmarks and Ranges is an absolute nightmare! We're now facing the challenges of word throwing up a modal dialogue box when being used from a service - (Anybody got an pointers here would be really good). The once thing that VSTO does give us is that if the solution turns out to be a total fiasco we can get the VSTO to run on the client's machine. One thing that we are also looking at is using Word 2003 on the client computer (installing the Office 12 compatibility pack) and on the server having an Office 12 document that we simply insert the correct XML in the pertinent places rather than modifying the object model. Regards Rob. -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Jonathan Heizer Sent: Saturday, May 05, 2007 5:29 AM To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: Re: [ADVANCED-DOTNET] Build RTF Document Yup, that's it. I was stripping out the rtf header info to try to fix it, but no luck. TX's license system is getting to be a bit out of hand. I am using this in a dll and the license has to be installed in the exe or it won't run. That is a bit of a pain in my situation so I am downloading Aspose now to try it out. -Jon -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Steve Welborn Sent: Friday, May 04, 2007 2:03 PM To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: Re: [ADVANCED-DOTNET] Build RTF Document Your project is similar to what mine what. I had to take multiple rtf files (we talked them into .doc files later on) and create one big file. So I ran into the same troubles as you in inserting one rtf document into the another. Sometimes it would work, but other times the font was off. I figured it had to do with the header in the second rtf file clashing with the header of the first document. That Aspose control did the trick. I just basically passed it the file path and name of the rtf (or doc)file and it handled all the inserting and saving. I basically put up to 33 documents into one document using it. And so far its been flawless. -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Jonathan Heizer Sent: Friday, May 04, 2007 2:44 PM To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: Re: [ADVANCED-DOTNET] Build RTF Document If you were the one that discussed this on here before I ran into it earlier. Aspose is in my list of ones to review. Right not I am looking at TX TextControl @ textcontrol.com since it is much cheaper. It looks like one of these two are going to be the way to go unless someone knows of a cheaper option. Thanks for the feedback, Jon -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Steve Welborn Sent: Friday, May 04, 2007 1:27 PM To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: Re: [ADVANCED-DOTNET] Build RTF Document Jon, I did a project that dealt with rtf files almost a year ago. I never had so much gray hair as I do now. About 6 months of working on it a fellow programming mentioned Aspose.Words (1) and it did took 2 weeks to implement the way we wanted and get the output we were looking for. Had I of had this at the start of the project I would have been done months sooner. I would highly suggest something like this. It handles .doc and .rtf. =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
