[Vishu Sukhdev]

Hi,
I used this code in WIndows xp its work fine

System.IO.Directory.CreateDirectory(Application.StartupPath + "\\Errors\\");

but when i install my software to other machine(Windows 7) i got error access denied.
so i manually Create Directory (Errors) in StartupPath so its work fine
so how to resolve this problem i don't want to create directory manually.

[Ändrew]

Try running it under administrator.

Example [From debug mode]

Project -> (Project Name) Properties -> Debug

Start Options

Command line arguments

Type in the textbox: runas

Example [Windows Vista/Seven]

Find the executable.
Right click on it and press Run as Administrator

Ändrew

This post has been edited by Ändrew: 16 March 2011 - 01:05 AM

[Vishu Sukhdev]

Actually I am maintaining errorlog if error occur in my application than Directory(Errors) create in my installation path and also crate a text file in Directory to write error details.

it's work fine in XP but when i installed setup of my software on WIndows 7 .
i aspected while error occur in my application at that time Directory and File should be Created in my installation path
but i got error " //Errors...access denied ".

[tlhIn`toq]

Repeating the problem description is unnecessary: We got it the first time.

Andrew already told you how to fix it: You need to run your application as Administrator.

[eclipsed4utoo]

Windows XP and Windows 7 handle security differently. Most applications, running under normal circumstances, will not have write access to the Program Files in Windows 7.

You need to either run the application as administrator(as Ändrew and tlhIn`toq stated), or create your directory in one of the user folders. Users will have write access to their "user" directory in Windows 7. This is where the Application Data and My Documents directories are located.

[raziel_]

You can check if the version of the windows is Vista or Higher and if so write it in different directory then application.startuppath:

if (Environment.OSVersion.Version.Major < 6)
{
  //'Its XP or less'
}
else
{
  //'Its vista or higher version of OS'
}

[Vishu Sukhdev]

Thank You Guys!

[raziel_]

One more thing if i may add. Here is interesting video on programing for standart user:
http://www.dreaminco...-standard-user/

In my opinion you have to make your program this way so that your program should not run as administrator. There are several restriction that you must follow when writing your program (the video covers most of them) but the least things are to not write/create files or folders in restricted folders. Dont write in the registry(you dont have the reason for doing this rly).

[Curtis Rutland]

There's folders designed specifically for this: the user app data folders. And guess what? There's a property that makes this path easily available to you:

Application.UserAppDataPath

You should already have permission there to write to a log.

[tlhIn`toq]

NoBrain, on 16 March 2011 - 07:15 AM, said:

Don't write in the registry(you dont have the reason for doing this really).

I don't know if I can agree with this. Maybe someday. But not this year. Its a nice theory, but the Registry was mean for holding persistent data and has been in use for years. Maintaining backward compatibility often necessitates its use. It's the one place guaranteed to be reachable where you expect it regardless of OS version, not affected by which user is logged in, easily organized in hierarchical node format and so on.

As much as MS says it's a bad practice, they themselves haven't gone away from it. They write to the registry in their latest OS and in all the Win7 applications they build. It's really hard to preach something when you can't follow it yourself.

[Curtis Rutland]

As long as you can clean up after yourself. Make sure that your installer's uninstall action kills any registry entries you've made, and then it's not that bad. Tens of thousands of orphaned keys are annoying though.

[marinus]

You can also give a directory full permission for system users in Program Files ,which is a quick way just for "testing" application code , but writing directly under C:\Folderpath
directory does not produce any errors in Win 7.

This post has been edited by marinus: 16 March 2011 - 08:43 AM

[raziel_]

tlhIn`toq, on 16 March 2011 - 05:18 PM, said:

NoBrain, on 16 March 2011 - 07:15 AM, said:

Don't write in the registry(you dont have the reason for doing this really).

I don't know if I can agree with this. Maybe someday. But not this year. Its a nice theory, but the Registry was mean for holding persistent data and has been in use for years. Maintaining backward compatibility often necessitates its use. It's the one place guaranteed to be reachable where you expect it regardless of OS version, not affected by which user is logged in, easily organized in hierarchical node format and so on.

As much as MS says it's a bad practice, they themselves haven't gone away from it. They write to the registry in their latest OS and in all the Win7 applications they build. It's really hard to preach something when you can't follow it yourself.

i`m sorry i thought that there was restrictions writing to the registry.

This post has been edited by NoBrain: 16 March 2011 - 08:49 AM

[JackOfAllTrades]

insertAlias, on 16 March 2011 - 11:35 AM, said:

As long as you can clean up after yourself. Make sure that your installer's uninstall action kills any registry entries you've made, and then it's not that bad. Tens of thousands of orphaned keys are annoying though.

That would be fab, if Microsoft and its ClickOnce technology for VSTO allowed me to do so This VSTO crap makes me leave all sorts of stuff behind that was created in the process of operation.

[Curtis Rutland]

ClickOnce is just good for little bullshit deployment. If you're going to do real deployments, make a real setup package. If you don't have the version of VS to do that, I'd suggest a third party installer. Nullsoft Installer is open source, I believe.