R
rivsys
I have a fair sized infopath app that must be deployed as fully trusted. The
application hits an Access backend. Data volumes are low, and the application
is replacing an unautomated Excel-based metrics gathering application. Data
security is not an important consideration and is managed by ACL at the
OS/server share level.
Application State:
All forms have been developed and published to a folder structure that
matches in every respect the user, folder structure and network addressing of
the ultimate target system at the client site.
All forms have virtually identical managed code (VB) statements. The
exceptions are trivial. All managed code compiles successfully.
All forms preview in multiple roles successfully on the development machine.
All forms have been run through regedit and all msi files are created
without errors.
The test machine is configured as follows: clean XP install, .Net Framework
1.1, all patches and service packs, and IP SP1. When redeploying test
installs, all test user profiles are deleted. All installs are run with the
"Just for me" option to insure no information is written to the registry
outside HKEY_CURRENT_USER. The server share containing the DB, msi, and VS
project files has been added to the Intranet security zone on the test
machine for all test users.
Installation Issues:
1) All msi installs fail with access denied error for any user NOT in the
test machine administrators group.
2) All msi installs complete successfully for users in the test machine
administrators group, with a single exception. The exception fails to install
with the error: "The following form template cannot be registered: [blah,
blah] because it contains a publish URL"
3) Of the 17 files successfully installed on the test machine, 3 fail to run
in infopath with "View1 is not valid XSL".
The client normally configures domain users as members of the local machine
administrators group, so item 1 is not a major issue. I'm just trying to
deploy as robust a solution as possible. A solution for Items 2 and 3 would
be nice as I would a) rather not have to rebuild these forms from scratch and
b) understand what idiotic move I pulled to cause the problem. Any ideas are
welcome.
Other Issues:
1) Has anyone built a routine to publish multiple forms simultaneously with
one pass through the wizard? One at time is a time consuming, boring, pain in
the patoot.
2) Has anyone built a VS.NET setup project that will convert multiple forms
to fully trusted URN and then build one single MSI file that will properly
register all forms in a project? Once again, step by step processes are
obviously a real productivity killer.
Thanks in advance for any help!
application hits an Access backend. Data volumes are low, and the application
is replacing an unautomated Excel-based metrics gathering application. Data
security is not an important consideration and is managed by ACL at the
OS/server share level.
Application State:
All forms have been developed and published to a folder structure that
matches in every respect the user, folder structure and network addressing of
the ultimate target system at the client site.
All forms have virtually identical managed code (VB) statements. The
exceptions are trivial. All managed code compiles successfully.
All forms preview in multiple roles successfully on the development machine.
All forms have been run through regedit and all msi files are created
without errors.
The test machine is configured as follows: clean XP install, .Net Framework
1.1, all patches and service packs, and IP SP1. When redeploying test
installs, all test user profiles are deleted. All installs are run with the
"Just for me" option to insure no information is written to the registry
outside HKEY_CURRENT_USER. The server share containing the DB, msi, and VS
project files has been added to the Intranet security zone on the test
machine for all test users.
Installation Issues:
1) All msi installs fail with access denied error for any user NOT in the
test machine administrators group.
2) All msi installs complete successfully for users in the test machine
administrators group, with a single exception. The exception fails to install
with the error: "The following form template cannot be registered: [blah,
blah] because it contains a publish URL"
3) Of the 17 files successfully installed on the test machine, 3 fail to run
in infopath with "View1 is not valid XSL".
The client normally configures domain users as members of the local machine
administrators group, so item 1 is not a major issue. I'm just trying to
deploy as robust a solution as possible. A solution for Items 2 and 3 would
be nice as I would a) rather not have to rebuild these forms from scratch and
b) understand what idiotic move I pulled to cause the problem. Any ideas are
welcome.
Other Issues:
1) Has anyone built a routine to publish multiple forms simultaneously with
one pass through the wizard? One at time is a time consuming, boring, pain in
the patoot.
2) Has anyone built a VS.NET setup project that will convert multiple forms
to fully trusted URN and then build one single MSI file that will properly
register all forms in a project? Once again, step by step processes are
obviously a real productivity killer.
Thanks in advance for any help!