Deploying .NET 2.0 Application to Network?

[E Jensen]

I am trying to deploy a .NET 2.0 Application to the network. However, I have
run into the Runtime Security Policy problem.

The whole point of deploying to the network instead of to each user's
machine was to decrease the amount of work involved in the initial deployment
and any future deployments.

I want to make the deployment process as easy as possible without leaving
gaping security holes.

I was wondering what the general consensus is on the best way to do this?

Is it easier to simply just deploy to each user's machine with an
auto-update feature built into the application?

Would it be better in the long run to strong name your assembly and use that
strong name with all your applications? Of course this would mean
configuring each user's machine to give sufficient permissions to that strong
name.

Or would it be sensible to just go the "not recommended" route of
configuring each user's machine to grant all permissions to applications run
from the intranet zone?
ClickOnce Deployment was suggested to me, but due to my environment, I
cannot afford to have users being required to make security decisions.

Also, I can't seem to include some files in the ClickOnce Deployment which
are required by the application, namely an INI file and some Crystal Reports
RPT files. Does anyone know how I can include those? When I press the
Application Files... button in the Publish section of the project properties,
I do not see these files in the list (including when I check Show all files).