Alternatives to Application.LocalUserAppDataPath

[illegal.prime]

Hi all, I would like to find a standard place to put application data,
but I don't want the pathname to include the application's version.

Any suggestions?

Thanks,
Novice

[Greg Young]

Why not use isolated storage and encapsulate access into its own assembly?
Then you would be using the version of the assembly used to acces isolated
storage.

This would allow you to re-release versions of the application without the
isolated storage changing providing that you didn't change anything to do
with the isolated storage. When you did change something with the isolated
storage that changed the way you stored data you would probably want to
migrate the data anyways (so up the version number of the assembly
encapsulating it).

Beyond that you can always create your own directory.

Cheers,

Greg Young
MVP - C#
http://codebetter.com/blogs/gregyoung
<il***********@gmail.comwrote in message
news:11*********************@75g2000cwc.googlegrou ps.com...

Hi all, I would like to find a standard place to put application data,
but I don't want the pathname to include the application's version.

Any suggestions?

Thanks,
Novice

[illegal.prime]

Actually for my purposes I want all versions of the the application to
be able to find and use the same file.

I've resolved this, by simply getting the parent directory that I get
from
Application.LocalUserAppDataPath

Thus removing the version information.

Thanks for your suggestion though - I had forgotten entirely about the
isolated storage feature of .NET.

Novice

Greg Young wrote:

Why not use isolated storage and encapsulate access into its own assembly?
Then you would be using the version of the assembly used to acces isolated
storage.

This would allow you to re-release versions of the application without the
isolated storage changing providing that you didn't change anything to do
with the isolated storage. When you did change something with the isolated
storage that changed the way you stored data you would probably want to
migrate the data anyways (so up the version number of the assembly
encapsulating it).

Beyond that you can always create your own directory.

Cheers,

Greg Young
MVP - C#
http://codebetter.com/blogs/gregyoung
<il***********@gmail.comwrote in message
news:11*********************@75g2000cwc.googlegrou ps.com...

Hi all, I would like to find a standard place to put application data,
but I don't want the pathname to include the application's version.

Any suggestions?

Thanks,
Novice