Thanks for the response, Gaurav. I followed the link you suggested, but don't
see an obvious answer there.

The first entry in
http://msdn2.microsoft.com/en-us/library/6s0wczt9(VS.80).aspx is the exact
error message we're seeing. That entry says the framework version must be the
same or newer than the computer the program was developed on.

The application was developed on my PC running framework 1.1.4322.573. The
tablet PCs are running framework 1.1.4322.573 as well.

We also have framework 2.0.50727.42 installed on our deskptop and laptop
PCs, but don't currently have it installed on the Tablet PCs (we will
eventually, we just left if off while we're trying to resolve this issue. At
least, under Administrative Tools it doesn't show up on the list (It looks
like the setup folks did install it, though, which you'll see from the lists
of installed software below... perhaps it isn't configured or something)

In the Add or Remove Programs listing on the desktop and laptop PCs, we have
the following:
Microsoft .Net Compact Framework 1.0 SP3 Developer
Microsoft .Net Compact Framework 2.0
Microsoft .Net Framework (English) v1.0.3705
Microsoft .Net Framework 1.0 Hotfix (KB886906)
Microsoft .Net Framework 1.1
Microsoft .Net Framework 1.1 Hotfix (KB886903)
Microsoft .Net Framework 2.0

On the Tablet PCs, we have the following:
Microsoft .Net Framework 1.1
Microsoft .Net Framework 1.1 Hotfix (KB886903)
Microsoft .Net Framework 2.0

Is it possible that the installed frameworks are conflicting, or that I'm
missing a piece?

In order to ensure that the application runs under the correct framework, I
added these lines to the web.config of the VSTO project:
<configuration>
<startup>
<supportedRuntime version="v1.1.4322"/>
<requiredRuntime version="v1.1.4322" safemode="true"/>
</startup>

Is there perhaps a problem with the exact wording there? I took the code out
a Knowledgebase article on the Microsoft site.

Thanks again for your help. I hope there isn't a basic incompatibility with
the Tablet PCs, since this is a crucial application.

Thanks,
Matt Underwood

[quoted text, click to view]