Installing data files with application?

[=?Utf-8?B?VHJhY2tz?=]

I include some sample binary data files (produced by my software) with my
application installation for the user to do what they want with. I put the
files in the Users Personal Data Folder/(myappsname) with VS 2005 installer -
File Types screen. All is well until the user changes the name of the file (I
want the user to be able to do this, move, or delete the files). When the
user changes the name, and then starts my application, the system tries to
re-install the file (and looks for the myaps.msi) instead of just starting my
application up. Not what I want. I dont care what the user does with the file.

I cant figure where this behavior is defined. Is there a "dont try to
re-install this file if deleted" setting in the installer part of VS 2005?

I have set the files and the folder as Vital = false and Tranistive = True
(or false). What am I missing or doing wrong?

Thanks,

Tom

[Cor Ligthert[MVP]]

Tom,

Not that I know this behaviour, however if you send a message about folders,
than please tell as well on what OS.

By instance Vista has a (let me say) very new folder behaviour

Cor
"Tracks" <Tr****@discussions.microsoft.comschreef in bericht
news:58**********************************@microsof t.com...

>I include some sample binary data files (produced by my software) with my
application installation for the user to do what they want with. I put the
files in the Users Personal Data Folder/(myappsname) with VS 2005
installer -
File Types screen. All is well until the user changes the name of the file
(I
want the user to be able to do this, move, or delete the files). When the
user changes the name, and then starts my application, the system tries to
re-install the file (and looks for the myaps.msi) instead of just starting
my
application up. Not what I want. I dont care what the user does with the
file.

I cant figure where this behavior is defined. Is there a "dont try to
re-install this file if deleted" setting in the installer part of VS 2005?

I have set the files and the folder as Vital = false and Tranistive = True
(or false). What am I missing or doing wrong?

Thanks,

Tom

[=?Utf-8?B?RmFtaWx5IFRyZWUgTWlrZQ==?=]

CMoya's approach is kind of what we do. We install zip files to a "support"
folder under the main app dir. On first run by a user, we unzip the files
using CSharpZip lib to the user's folder.

Occasionally where we have huge data files (1GB+) we write a custom action
to install the data to a common for all users.

VS Deployment projects care about the zip files, but not the contents after
they are extracted, even when within a custom action.

I hope this helps.

"Tracks" wrote:

I include some sample binary data files (produced by my software) with my
application installation for the user to do what they want with. I put the
files in the Users Personal Data Folder/(myappsname) with VS 2005 installer -
File Types screen. All is well until the user changes the name of the file (I
want the user to be able to do this, move, or delete the files). When the
user changes the name, and then starts my application, the system tries to
re-install the file (and looks for the myaps.msi) instead of just starting my
application up. Not what I want. I dont care what the user does with the file.

I cant figure where this behavior is defined. Is there a "dont try to
re-install this file if deleted" setting in the installer part of VS 2005?

I have set the files and the folder as Vital = false and Tranistive = True
(or false). What am I missing or doing wrong?

Thanks,

Tom

[=?Utf-8?B?VHJhY2tz?=]

Thanks,

It does it in Vista Home Premium and XP something and others. So I assume
all that the .net 2 framework runs on.

Yeah I am up on the Vista issues some and how the folders have changed. It
is not that cause I am having the same thing on XP? More in next response.

"Cor Ligthert[MVP]" wrote:

Tom,

Not that I know this behaviour, however if you send a message about folders,
than please tell as well on what OS.

By instance Vista has a (let me say) very new folder behaviour

Cor
"Tracks" <Tr****@discussions.microsoft.comschreef in bericht
news:58**********************************@microsof t.com...

I include some sample binary data files (produced by my software) with my
application installation for the user to do what they want with. I put the
files in the Users Personal Data Folder/(myappsname) with VS 2005
installer -
File Types screen. All is well until the user changes the name of the file
(I
want the user to be able to do this, move, or delete the files). When the
user changes the name, and then starts my application, the system tries to
re-install the file (and looks for the myaps.msi) instead of just starting
my
application up. Not what I want. I dont care what the user does with the
file.

I cant figure where this behavior is defined. Is there a "dont try to
re-install this file if deleted" setting in the installer part of VS 2005?

I have set the files and the folder as Vital = false and Tranistive = True
(or false). What am I missing or doing wrong?

Thanks,

Tom

[=?Utf-8?B?VHJhY2tz?=]

I see. Thanks.

I was debating something like that also.

It still seems to me there is something not right here.

Does the unzip method work properly in Vista? What if there are two or more
users on one PC or Network? Does your program keep track of which users had
the files extracted into their local user folder? And if the user changes
their name does your program figure that out too? Just thinking out loud here.
"Family Tree Mike" wrote:

CMoya's approach is kind of what we do. We install zip files to a "support"
folder under the main app dir. On first run by a user, we unzip the files
using CSharpZip lib to the user's folder.

Occasionally where we have huge data files (1GB+) we write a custom action
to install the data to a common for all users.

VS Deployment projects care about the zip files, but not the contents after
they are extracted, even when within a custom action.

I hope this helps.

"Tracks" wrote:

I include some sample binary data files (produced by my software) with my
application installation for the user to do what they want with. I put the
files in the Users Personal Data Folder/(myappsname) with VS 2005 installer -
File Types screen. All is well until the user changes the name of the file (I
want the user to be able to do this, move, or delete the files). When the
user changes the name, and then starts my application, the system tries to
re-install the file (and looks for the myaps.msi) instead of just starting my
application up. Not what I want. I dont care what the user does with the file.

I cant figure where this behavior is defined. Is there a "dont try to
re-install this file if deleted" setting in the installer part of VS 2005?

I have set the files and the folder as Vital = false and Tranistive = True
(or false). What am I missing or doing wrong?

Thanks,

Tom

[=?Utf-8?B?VHJhY2tz?=]

I see. A local user variable setting was what I was forgetting. Got those
and know how to use em! Sorta. I will try it.

Thanks for explaining,

Tom
"CMoya" wrote:

Once again,
1) Have Setup install the files (forget zip for now) into your APP FOLDER.
2) Create a Setting in your app (My Project -Settings) called FirstRun and
scoped to USER.
3) When your app (your APP.EXE) runs check the setting and copy the files to
the users profile (where it will remain regardless of anything). (If
My.Settings.FirstRun Then CopyFiles...).
4) Set the setting so you don't do it again for that user. When a new user
comes along his setting wont be set.

This really isn't all that difficult. Maybe I'm missing something? :)