Hi, Do yourself and your team a favor and consider a distributed computing approach in general and 'smart client architecture' in particular, make better use of client-side investment with office automation and client-side processing. Try to decompose your policy and behavior as services in the first place (if these finish being implemented as web services or not is an entirety different matter)
The Visual Studio Tools for Office is very helpful and the next version would be better, among other things, a similar ASP.NET-like 'code-behind' model with managed code and Office documents give finer control. Consider de XML capabilities of Office 2003 for mandatory server-side processing. Look at: http://msdn.microsoft.com/office/ http://msdn.microsoft.com/smartclient/ http://msdn.microsoft.com/architecture/ Best regards, -----Original Message----- From: Unmoderated discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Little Sent: Sunday, December 26, 2004 9:31 AM To: [email protected] Subject: [ADVANCED-DOTNET] Design Choices My current assignment is a Project Management system for a large enterprise. This will involve a substantial amount of data entry and document manipulation. Specifically, they have about 150 Word document templates that they use to generate various documents in the course of a project. They want the generation of these documents to be reasonably automatic. This is Phase I of a project that will gradually grow to encompass a wider spectrum of functionality. Part of the requirement spec was that the application should be entirely web-based. However, as I have delved deeper into things, I am questioning whether or not to separate out the major data entry and document manipulation tasks as a Windows app, assuming that there is a network resource that all can access. I would then use the web interface as a largely read-only, or limited data entry mechanism for those areas that require it. (This is an intranet deployment, not internet). I have read the various articles warning against using true Word automation on the server, and I certainly don't want to store all of the document templates and resulting documents on the web server. I could probably generate some client-side scripting to have the document manipulation done on the client side, but I am just wondering if I am trying to hammer a square peg into a round hole here. >From a performance and security angle, what are your thoughts on this? Jeff =================================== This list is hosted by DevelopMentor(r) http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor� http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
