Results 1 to 5 of 5

Thread: [RESOLVED] [02/03] Setup Project & Registry Entries

  1. #1

    Thread Starter
    Hyperactive Member
    Join Date
    Sep 2005
    Posts
    384

    Resolved [RESOLVED] [02/03] Setup Project & Registry Entries

    I have a program (wow). I've created a setup project for it, and everythings install perfectly and the program runs perfectly, thus far.
    I make use of three registry keys in my program, and I save small bits of info in there.

    I have noticed, with each new "update" of my program, that I have to manually go into the registry, and create these three keys again, and set their values again. This is because of the the (I think it's the program's version number), that keeps changing with each new build. It is frustrating me, because I would like to always save to the [b]same[/] registry key, irrespective of what the program's version number is.

    How should I go about fixing it?
    Should I set up the keys & values through my setup project? If so, How?
    Or is there a different way?

  2. #2
    I'm about to be a PowerPoster! Hack's Avatar
    Join Date
    Aug 2001
    Location
    Searching for mendhak
    Posts
    58,333

    Re: [02/03] Setup Project & Registry Entries

    Moved To Application Deployment

  3. #3
    I'm about to be a PowerPoster! kleinma's Avatar
    Join Date
    Nov 2001
    Location
    NJ - USA (Near NYC)
    Posts
    23,373

    Re: [02/03] Setup Project & Registry Entries

    Are your registry entires being written by your program or by the installer.

    Also what methods are you using for registry writing?

  4. #4

    Thread Starter
    Hyperactive Member
    Join Date
    Sep 2005
    Posts
    384

    Re: [02/03] Setup Project & Registry Entries

    I write to the registry from my application itself, via Application.UserAppDataRegistry

    I've noticed that in my AssemblyInfo.vb file that I had something like this:
    Code:
    <Assembly: AssemblyVersion("1.0.*")>
    Do you think, that is what is causing this?

    I've changed it now to:
    Code:
    <Assembly: AssemblyVersion("2.0.135.789")>
    But haven't tested it yet, but will it be fixed then?

    Sorry for posting in the wrong forum, I never knew about the Application Deployement forum

  5. #5

    Thread Starter
    Hyperactive Member
    Join Date
    Sep 2005
    Posts
    384

    Re: [02/03] Setup Project & Registry Entries

    OK, I feel dumb

    It was because of the Assemblyversion Number.

    Thanx anyways gents!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width