Should I use a registry or a flat file to save the state of the program?

Question

We have many products that maintain their “state” in the registry.

What is the best practice for maintaining program states? What are the advantages / disadvantages of saving program states like registry entries or saving program states to a flat file, such as XML?

Thank!

Answer 1

The obvious answer would be to save these states in a regular file, which makes it easier for users to manually backup / restore the state.

Answer 2

Also note that there are several keys in the registry that are special for each user in the system.

, - , , ​​(, , ). , .

Answer 3

, . , - , , Vista UAC.

, .Net, Windows . , , , , , , .

, , , () . . UAC , , .

Answer 4

.

( , "" Windows?)

( ) . , ..

, "", " /", . , , , .

Answer 5

. .INI . , . , .INI .

(/?). . , .

, . Windows/// ( ). c:\program files, . , , c:\user data, ( tweakui power toy regedit ( - )).

- Windows , re-insatll ( ), C:

Windows, . , , , , , .

Imo, , - Windows, - .

? . INI, , , .

, ...

Answer 6

, , INI XML . , , . , , , , .

Answer 7

, =)

io vs , /
/ / /

,

Answer 8

, . - XCopy-Deployable, . .ini( - INI, .net )

, (, Windows), "" , , . , , C:\Program Files , . , (% APPDATA% , , Silverlight), " ".

, Mono, Registry Flat Files.