By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,534 Members | 1,830 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,534 IT Pros & Developers. It's quick & easy.

.Net Application on share with permission List Folder/Read Data not allowed results in .Net Framework Initialization error

P: n/a
I have a VS2005 VB.Net windows form application deployed to a share drive.
The windows explorer security permissions for this application (.exe) file
is set for Everyone with List Folder/Read Data not allowed. This is done so
that users cannot take away a copy of the .exe file. When I execute the
..exe from the client computer I get .Net Framework Initialization Error,
Unable to find a version of the runtime to run this application. The other
permissions are set as follows: Traverse Folder/Execute File is allowed,
Read Attributes is allowed, Read Permissions is allowed, all others not
allowed. The above settings works for VB6 applications but not the .Net
application. If I set the permission List Folder/Read Data to allow, the
..Net application works fine (but of course a user can now copy the program).

The client and server computers are both WinXP, SP2, with .Net Framework
2.0, peer to peer network. The .Net Framework Runtime Security Policy on
the client machine is set for FullTrust for URL pointing to the share and
has been tested.

Any ideas on how to set this up correctly so the .Net app will run from a
share with the .exe permission set to List Folder/Read Data not allowed?

Bill

Mar 10 '07 #1
Share this Question
Share on Google+
2 Replies


P: n/a
When the desktop app is located on a network share, it does not run on the
computer where the share belongs to, it is copied from the share (hence
being read) to the running computer's memory and run. So, if you do not the
app's files to be read, then you cannot run it. Period. IMO, this is not the
way to "protect" your work from being copied. You need to find some other
means for that purpose.
"Bill Fallon" <bi**@fallonmarine.comwrote in message
news:H2AIh.129$I56.117@trnddc06...
>I have a VS2005 VB.Net windows form application deployed to a share drive.
The windows explorer security permissions for this application (.exe) file
is set for Everyone with List Folder/Read Data not allowed. This is done
so that users cannot take away a copy of the .exe file. When I execute the
.exe from the client computer I get .Net Framework Initialization Error,
Unable to find a version of the runtime to run this application. The other
permissions are set as follows: Traverse Folder/Execute File is allowed,
Read Attributes is allowed, Read Permissions is allowed, all others not
allowed. The above settings works for VB6 applications but not the .Net
application. If I set the permission List Folder/Read Data to allow, the
.Net application works fine (but of course a user can now copy the
program).

The client and server computers are both WinXP, SP2, with .Net Framework
2.0, peer to peer network. The .Net Framework Runtime Security Policy on
the client machine is set for FullTrust for URL pointing to the share and
has been tested.

Any ideas on how to set this up correctly so the .Net app will run from a
share with the .exe permission set to List Folder/Read Data not allowed?

Bill

Mar 11 '07 #2

P: n/a
It is only the VB.Net application that will not run from a share when the
permission is set to List Folder/Read Data not allowed. VB6 and Fortran
applications run just fine from the share when the permission is set to List
Folder/Read Data not allowed. Why is that the case? Could there be some
special setting in .Net that will make this work?

Bill

"Norman Yuan" <No*****@NotReal.notwrote in message
news:uM****************@TK2MSFTNGP03.phx.gbl...
When the desktop app is located on a network share, it does not run on the
computer where the share belongs to, it is copied from the share (hence
being read) to the running computer's memory and run. So, if you do not
the app's files to be read, then you cannot run it. Period. IMO, this is
not the way to "protect" your work from being copied. You need to find
some other means for that purpose.
"Bill Fallon" <bi**@fallonmarine.comwrote in message
news:H2AIh.129$I56.117@trnddc06...
>>I have a VS2005 VB.Net windows form application deployed to a share drive.
The windows explorer security permissions for this application (.exe) file
is set for Everyone with List Folder/Read Data not allowed. This is done
so that users cannot take away a copy of the .exe file. When I execute
the .exe from the client computer I get .Net Framework Initialization
Error, Unable to find a version of the runtime to run this application.
The other permissions are set as follows: Traverse Folder/Execute File is
allowed, Read Attributes is allowed, Read Permissions is allowed, all
others not allowed. The above settings works for VB6 applications but not
the .Net application. If I set the permission List Folder/Read Data to
allow, the .Net application works fine (but of course a user can now copy
the program).

The client and server computers are both WinXP, SP2, with .Net Framework
2.0, peer to peer network. The .Net Framework Runtime Security Policy on
the client machine is set for FullTrust for URL pointing to the share and
has been tested.

Any ideas on how to set this up correctly so the .Net app will run from a
share with the .exe permission set to List Folder/Read Data not allowed?

Bill

Mar 11 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.