automation

Intro In my current project we use Azure Resource Manager (ARM) templates to help with deployments across multiple subscriptions and environments. One of the elements of the ARM template is adding a couple of Shared Access Policies to enable Read and Write on the queues we have in place. The policies have been defined on Service Bus level because they span multiple queues. Our ARM template functioned just fine, (automated) deployment was up & running and life was beautiful.

When building an ASP application that generates Word documents, it was working fine on the local machine: A Windows XP installation with Office 2007. When we deployed it to windows 2008 (64 bit) and Word 2007 we saw that Documents.Open returned null. Other than this, there are no exceptions. The code that returned the error (simplified): Application app = new Application(); Document doc = app.Documents.Open(ref name); As it turns out, a 64 bit system stores temporary files in C:\Windows\Sys\WOW64\config\system\profile\Desktop folder.