![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
![]() |
| |
| | #1 (permalink) |
| | I can't execute my own executable I have written a program, say "AAA", which detects its folder, extracts some info from the folder's name, and does a number of updates based on that. It works great. Whenever I put it on the network, though, it won't execute at all - it crashes. Let's say some other code copies AAA.exe in the folder W:\EPS\DataOutput 2009\...\...\Run 1 for Req RBPIFF On execution, the code in AAA should read the string RBPIFF and do some work based on this code, "RBPIFF" Next, that other code would copy AAA.exe to the folder W:\EPS\DataOutput 2009\...\...\Run 1 for Req AMAFFW Now the code should read the string AMAFFW and do some work based on this code, "AMAFFW"... and so on - all the folders in which this AAA.exe will reside will have the form W:\EPS\DataOutput 2009\...\...\Run x for Req abcdef The problem is that as soon as I copy AAA.exe to the network, on execution, first I have a message saying "The publisher could not be verified. Are you sure blah blah ?" I say Run. Then I get a crash. I have commented out ALL MY CODE IN THIS app - all of it. Now it should only show an empty, grey, form, Form1. It doesn't. It still crashes. Assuming that the user already has the framework 2.0 installed, how can I create in dotnet a "portable" executable, which would be copied from folder to folder on this server, would detect its parent folder's name, as described above, and would do some work based on that name ? On my local machine it works great. However.... Please help. Thank you very much Alex |
My System Specs![]() |
| | #2 (permalink) |
| | Re: I can't execute my own executable This have to do with permission to run executable on network. see this article: http://www.west-wind.com/WebLog/posts/275.aspx "Radu" <cuca_macaii2000@xxxxxx> wrote in message news:1b7fcf8d-d747-4a2c-8ae4-146d3431563d@xxxxxx Quote: >I have written a program, say "AAA", which detects its folder, > extracts some info from the folder's name, and does a number of > updates based on that. It works great. > > Whenever I put it on the network, though, it won't execute at all - it > crashes. > > Let's say some other code copies AAA.exe in the folder > W:\EPS\DataOutput 2009\...\...\Run 1 for Req RBPIFF > On execution, the code in AAA should read the string RBPIFF and do > some work based on this code, "RBPIFF" > > Next, that other code would copy AAA.exe to the folder > W:\EPS\DataOutput 2009\...\...\Run 1 for Req AMAFFW > Now the code should read the string AMAFFW and do some work based on > this code, "AMAFFW"... > > and so on - all the folders in which this AAA.exe will reside will > have the form > W:\EPS\DataOutput 2009\...\...\Run x for Req abcdef > > > The problem is that as soon as I copy AAA.exe to the network, on > execution, first I have a message saying "The publisher could not be > verified. Are you sure blah blah ?" I say Run. Then I get a crash. > > I have commented out ALL MY CODE IN THIS app - all of it. Now it > should only show an empty, grey, form, Form1. It doesn't. It still > crashes. > > Assuming that the user already has the framework 2.0 installed, how > can I create in dotnet a "portable" executable, which would be copied > from folder to folder on this server, would detect its parent folder's > name, as described above, and would do some work based on that name ? > On my local machine it works great. However.... > > Please help. > Thank you very much > Alex |
My System Specs![]() |
![]() |
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| Executable files | Vista mail | |||
| Execute error: Type Mismatch: 'Execute' | VB Script | |||
| run executable | PowerShell | |||
| Executable | Vista General | |||
| Signing an executable | Vista security | |||