App deployment across Domain PCs

Question

0.00/5 (No votes)

See more:

hi guys,
i just recently built a survey application that is supposed to be deployed by our SYSADMIN guys to reflect on all users in the domain. i have managed to deploy it and it keeps showing on some user's profile and not all.
some of the present issues are:

1. SQLClient security permission error
2. dotNet framework incompatibility
3. some users still dont see the survey

the app is supposed to run during user logon as the script that calls it is attached to every user's profile.

the application was built with VS 2005 (.NET framework 2.0)

any help will be glad appreciated.

thanks

Posted 4-Sep-10 2:38am

waizkode

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Accepted Answer · 2010-09-08T18:19:00

The .NET Framework 2.0 has to be installed on every users machine. Apparently, this is not the case.

If the .EXE is being run from a network share, the .NET CLR to run the app in a highly restricted sandbox since non-local locations for executable code is not trusted, by default. This can be fixed in a variety of ways, but it comes down to configuring trusts. Usually, this is done by telling the CLR to trust all code signed with a certain certificate or (not so securely) trust any code running from a certain network location.

The trust issue will throw the permissions exception when trying to run SQL connection and query code.