Re: VB.NET Deployment - Checking for user-modified files
From: SStory (TheStorys_at_TAKEOUTTHISSPAMBUSTERsofthome.net)
Date: 02/26/04
- Next message: SStory: "building vb.net with nant"
- Previous message: Microsoft: "Directory Properties"
- In reply to: Juggler: "Re: VB.NET Deployment - Checking for user-modified files"
- Next in thread: David Guyer [MS]: "Re: VB.NET Deployment - Checking for user-modified files"
- Reply: David Guyer [MS]: "Re: VB.NET Deployment - Checking for user-modified files"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 25 Feb 2004 19:57:40 -0600
There may be... I haven't been using it enough to do formal updates yet.
Simple updates are send them the new exe and they copy over the old one.
Pretty neat, but...
Maybe if there is a way someone at Microsoft or some other guru will respond
and tell us both.
Sorry I don't know more.
Shane
"Juggler" <anonymous@discussions.microsoft.com> wrote in message
news:618533F6-E898-4503-B1C0-AE781942C35A@microsoft.com...
> I think I'm going to try including the .mdb file with the program, but in
a sub-folder. The program will check to see if the .mdb file exists where it
should during normal operation, and if it isn't there (i.e. they just
installed the program), it will copy the .mdb file from the sub-directory
and put it in the proper place before it calls it for the first time.
>
> Hopefully, it will all work out. It still seems silly that there isn't a
simple setting in vb.net that checks whether or not a file has been modified
since the last version update, and to leave it alone if the user has
modified it.
>
> Juggler
>
> ----- SStory wrote: -----
>
> I like this idea best.
>
> Throw it on the CD... Require them to insert CD first time or
whatever and
> your program checks to see if it is there using
> the fileinfo class and then if not copies it from CD to disk..
>
> Seems the easiest although setup may have a way.. I don't know
>
> Shane
>
> "Ot" <uraza@tds.invalid (use net)> wrote in message
> news:%23xfXvGw%23DHA.2308@tk2msftngp13.phx.gbl...
> > In a similar situation, I did not deliver the default data as part
of the
> > application, but instead built it from the application itself when
it did
> > not exist. That is, the application itself checks for data
existing and
> > builds the default template that way. You could include the
default data
> > as an embedded resource and create it where you want when you want.
> >>> "Juggler" <anonymous@discussions.microsoft.com> wrote in message
> > news:4FEB069A-B662-4543-9150-7ECFDBAE3157@microsoft.com...
> >> I'm using vb.net 2002.
> >>>> When I go to the File System Editor, highlight the file and
select
> > properties, I have the option to adjust:
> >>>> - Condition (seems to only check version/processor info on the
computer
> > being installed on)
> >> - Exclude (blanket exclude from installation)
> >> - Folder (where to install it)
> >> - Hidden (is it a hidden file)
> >> - PackageAs (not sure what this is for)
> >> - Permenent (whether or not to leave it during uninstallation)
> >> - ReadOnly (read only)
> >> - SharedLegacyFile (this might be it, but I don't really know what
the
> > help text is talking about)
> >> - SourcePath (file location)
> >> - System (is it a system file?)
> >> - TargetName (name of file)
> >> - Transitive (whether or not the installer should reevaluate the
> > Condition property each installation)
> >> - Vital (whether a file is vital for installation or not)
> >>>> There must be an answer out there. It's like saving a user's
preferences
> > from version to version. Each time I release a new version of the
program,
> > I don't want the users to have to re-enter their info. I can work
around
> > the installation problem with preferences by using a text file for
the
> > user's preferences. When the program loads the splash screen, I
check for
> > the existance of the preferences text file. If it's not there, I
can
> > display a window to the user that asks for their preferences
information
> > (name, whether they want to print in color, etc.), and then write a
text
> > file.
> >>>> Thanks for any help that can be provided!
> >>>> Juggler (@)at sonic (.) net
> >>>> ----- SStory wrote: -----
> >>>> Well, I assume you are upgrading using a setup in vb.net
2003?
> >>>> If so isn't there a property for the file whatever.mdb to
not
> > overwrite?
> >>>> Of course from within VB.NET you have the
system.io.fileinfo class
> > to get
> >> information on files... but that doesn't seem that it would
do much
> > good as
> >> far as setup goes.
> >>>> Check to see if you can't highlight the .MDB file in the
setup and
> > click
> >> properties and set to not overwrite. don't have the IDE open
at
> > present but
> >> that is where I would look.
> >>>> HTH,
> >>>> Shane
> >>>> "Juggler" <anonymous@discussions.microsoft.com> wrote in
message
> >> news:FECA2F8F-B95D-4808-88DC-D40C1624AFA9@microsoft.com...
> >>> Hi all,
> >>>> I've written a program in VB.NET that allows the user to build
> > quotes for
> >> installing shower enclosures. As part of the program, I've
included
> > a blank
> >> Access database. I've provided them with an interface where
they
> can
> > add
> >> their own clients to the database.
> >>>> When the user upgrades to a newer version of my program, I don't
> > want the
> >> installer to overwrite the Access database file with my blank
one
> > again. How
> >> can I tell VB.NET to check to see if the file has been
modified,
> and
> > if so,
> >> not to overwrite it?
> >>>> Many thanks,
> >>>> Juggler at(@) sonic dot(.) net
> >>>>>>>>
- Next message: SStory: "building vb.net with nant"
- Previous message: Microsoft: "Directory Properties"
- In reply to: Juggler: "Re: VB.NET Deployment - Checking for user-modified files"
- Next in thread: David Guyer [MS]: "Re: VB.NET Deployment - Checking for user-modified files"
- Reply: David Guyer [MS]: "Re: VB.NET Deployment - Checking for user-modified files"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
