naxoccupy.blogg.se

The ability to read and write Office documents without going through the object model of the hosting Office application becomes far more desirable in a server-side scenario. That's because Office desktop applications such as Word and Excel were never designed to run on the server, and they require a custom utility program to terminate and restart them whenever they encounter a modal dialog that requires human intervention. Anyone who has spent time writing the extra infrastructure code required to make an Office desktop application behave reliably on the server will tell you it's a less than desirable solution. The vast majority of production applications that read and write Office documents do so by going through the object model of the hosting Office application.Īpplications and components that use the object model of applications such as Word or Excel run much better on the desktop than they do in server-side scenarios. However, this binary file format has proven to be too tricky to work with.

The older binary format used by Microsoft Word, Excel®, and PowerPoint® was introduced in 1997 and has remained the default file format up through the Office 2003 release. Until now, writing and deploying server-side applications that read, modify, and generate documents used by Microsoft® Office applications has presented a challenge. Code download available at: BasicInstincts2006_11.exe(170 KB)