I tried to do whatever was on the link. We used micrsoft.net framework 2000.
I'm using the vb software on the computer harddrive and save vb file is on the harddrive on the local network. So the link you gave me didnt work. I tried but it only works when i copy the vb project file to the desktop and run it.
i select full trust and everything i could. It would work if the file was on the c drive but if the file stay on W drive for local network then it wouldn't work.
That's by design. If the assemblies are C: then they are automatically given full trust, if the assemblies are on another drive then they are not.
When you went to trust your assemblies, where were they at the time, on the C: drive or on the network If they were on the C:, follow the steps again but trust the ones on the network.
Also, are you recompiling the code everytime you attempt to run it If so, can you paste the contents of your AssemblyInfo.cs/AssemblyInfo.vb file, especially the AssemblyVersion attribute.
ok this is how i did it. I went to Framework2.0 then selected increase trust assembly. Then selected for this computer. Then i selected the w:\project\bin\debug\name.exe.vhost(dont remember exactly directory path but that pretty much how it should be). Then clicked next, then clicked full trust. Then i clicked save all before i recompile. So then i pressed rebuild on vb, then start debugging. Then that message pop up.
I'm sorry because im not at work right now so i couldn't get the code.
Well, the software got
install in c drive. but the folder that contain the files are in local
network harddrive. And the semicolon at the end does not help much. I did
try to change that. But it still didnt help.
Help plz
shahry baba
jianfeng
Hey David,
I tried to do whatever was on the link. We used micrsoft.net framework 2000.
I'm using the vb software on the computer harddrive and save vb file is on the harddrive on the local network. So the link you gave me didnt work. I tried but it only works when i copy the vb project file to the desktop and run it.
Could you help me thanks
Vivek S
AndyCadley
batub
Microsoft .NET Framework 2000 Are you sure you don't mean .NET Framework 2.0
Did you follow the exact steps given
Boomstick
That's by design. If the assemblies are C: then they are automatically given full trust, if the assemblies are on another drive then they are not.
When you went to trust your assemblies, where were they at the time, on the C: drive or on the network If they were on the C:, follow the steps again but trust the ones on the network.
Also, are you recompiling the code everytime you attempt to run it If so, can you paste the contents of your AssemblyInfo.cs/AssemblyInfo.vb file, especially the AssemblyVersion attribute.
M Witlox
Grant_Holliday
hi,
first of all to get answer you have to edit your message title (look to the top of this forum how to get optimal answer")
in your connection string
"Provider=Microsoft.Jet.OLEDB.4.0;" & _
"Data Source=C:\Data.mdb;"
i guess you have to remove the last ";"
best regards
Lexicon
ok this is how i did it. I went to Framework2.0 then selected increase trust assembly. Then selected for this computer. Then i selected the w:\project\bin\debug\name.exe.vhost(dont remember exactly directory path but that pretty much how it should be). Then clicked next, then clicked full trust. Then i clicked save all before i recompile. So then i pressed rebuild on vb, then start debugging. Then that message pop up.
I'm sorry because im not at work right now so i couldn't get the code.
PS: the data.mdb file is on the W drive also.
kapil kumar P
Scott Grosch
Jatin Zalavadia
When you get home, as I stated above, post the contents of AssemblyInfo.cs/AssemblyInfo.vb.
If you are recompiling after you trust the assemblies, and your AssemblyVersion is changing every compile, then it won't work.
Also you want to trust your assemblies, not the 'name.vshost.exe' file as this is used only by Visual Studio.
jriker1
That's the issue, by default, .NET runs applications run from the network with lower permissions, than if it was run locally.
Have a look at the following post, which will give you more information:
Why do I get a SecurityException when running from the network
carlpicanco