Re: Standalone VB.Net app?


Mr. JackBlack,

What is your application trying to do? What is reporting the security
errors or how are the errors being reported to you?

You may already know this, but... Some application behavior requires
administrative privileges to perform their activities. For example,
the logged in user may not have the correct permissions to modify the
registry; if your application is attempts to create a key it will fail
due to permissions. Are you running the application on the other boxes
using the same domain account?

Some application behavior requires administrative privledges
JackBlack wrote:
Hi, all! Trying to build a stand-alone vb.net app (from VS.Net 2k5) that
will let me just take the EXE from the dev box over to a client box and run
it, as-is, without "installing" it. I was under the assumption that this
was still possible, but I seem to get security errors on client boxes when I
just run the EXE on the client machine. Even after tweaking the ClickOnce
settings to specfically allow the type that's giving me the error, I still
get it. The only way to prevent the errors is to do a typical install (run
the setup.exe), which defeats the whole purpose in the first place.

What's the trick? Workstations are all Xp/Pro, latest patches (including
Framework 2.0), running inside a Win2k3 domain (users do NOT have
administrative privilege locally). Help!! :)

Jack

.

Relevant Pages
Quantcast