If not the registy, then what?

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • SQLScott

    If not the registy, then what?

    In all the books I have read on .Net, they all recommend that using the
    registry in .net is the "old" way. OK, i'll buy that, but hey don't way what
    the new way is. Can anyone point me in the right direction?

    --
    Thanks,

    Scott
  • Mythran

    #2
    Re: If not the registy, then what?

    XML Configuration files :)

    I use the registry, still, for quite a few things that need to be stored
    user-wide for multiple applications that do not have a common shared directory
    (IE: Server-Based software and ASP.Net Software). Anywho, check out the XML
    config files in MSDN :)

    Sorry no links, no time to look em up.

    Mythran


    "SQLScott" <SQLScott@discu ssions.microsof t.com> wrote in message
    news:A50B2370-230B-4DFF-8409-F24420BCD734@mi crosoft.com...[color=blue]
    > In all the books I have read on .Net, they all recommend that using the
    > registry in .net is the "old" way. OK, i'll buy that, but hey don't way what
    > the new way is. Can anyone point me in the right direction?
    >
    > --
    > Thanks,
    >
    > Scott[/color]


    Comment

    • Mythran

      #3
      Re: If not the registy, then what?

      XML Configuration files :)

      I use the registry, still, for quite a few things that need to be stored
      user-wide for multiple applications that do not have a common shared directory
      (IE: Server-Based software and ASP.Net Software). Anywho, check out the XML
      config files in MSDN :)

      Sorry no links, no time to look em up.

      Mythran


      "SQLScott" <SQLScott@discu ssions.microsof t.com> wrote in message
      news:A50B2370-230B-4DFF-8409-F24420BCD734@mi crosoft.com...[color=blue]
      > In all the books I have read on .Net, they all recommend that using the
      > registry in .net is the "old" way. OK, i'll buy that, but hey don't way what
      > the new way is. Can anyone point me in the right direction?
      >
      > --
      > Thanks,
      >
      > Scott[/color]


      Comment

      • Cor Ligthert

        #4
        Re: If not the registy, then what?

        Scott,

        Maybe you can check if Microsoft uses the registry, check for the word
        Microsoft by instance in that.

        It is in my opinion is the registry not a seperated database so you should
        only store in that things, what real acts with the computer. However for
        clientcomputer depended things is it in my opinion a good store.

        XML is good for settings which are not good hardcoded in the program however
        have to be set by instance in advance. What is a XML file more than a new
        way of the INI file, from which is so often writen that there was a new
        successor for that, "the registry".

        However, just my thought.

        Cor

        "SQLScott" <SQLScott@discu ssions.microsof t.com>
        [color=blue]
        > In all the books I have read on .Net, they all recommend that using the
        > registry in .net is the "old" way. OK, i'll buy that, but hey don't way
        > what
        > the new way is. Can anyone point me in the right direction?
        >
        > --
        > Thanks,
        >
        > Scott[/color]


        Comment

        • Cor Ligthert

          #5
          Re: If not the registy, then what?

          Scott,

          Maybe you can check if Microsoft uses the registry, check for the word
          Microsoft by instance in that.

          It is in my opinion is the registry not a seperated database so you should
          only store in that things, what real acts with the computer. However for
          clientcomputer depended things is it in my opinion a good store.

          XML is good for settings which are not good hardcoded in the program however
          have to be set by instance in advance. What is a XML file more than a new
          way of the INI file, from which is so often writen that there was a new
          successor for that, "the registry".

          However, just my thought.

          Cor

          "SQLScott" <SQLScott@discu ssions.microsof t.com>
          [color=blue]
          > In all the books I have read on .Net, they all recommend that using the
          > registry in .net is the "old" way. OK, i'll buy that, but hey don't way
          > what
          > the new way is. Can anyone point me in the right direction?
          >
          > --
          > Thanks,
          >
          > Scott[/color]


          Comment

          • Mythran

            #6
            Re: If not the registy, then what?


            "Cor Ligthert" <notmyfirstname @planet.nl> wrote in message
            news:%23XE4YNYo EHA.692@TK2MSFT NGP12.phx.gbl.. .[color=blue]
            > Scott,
            >
            > Maybe you can check if Microsoft uses the registry, check for the word
            > Microsoft by instance in that.[/color]
            Ummm, of course they do :P

            [color=blue]
            >
            > It is in my opinion is the registry not a seperated database so you should
            > only store in that things, what real acts with the computer. However for
            > clientcomputer depended things is it in my opinion a good store.
            >[/color]
            Depends on the key and what the data is. When you run a windows setup file
            (Windows Installer), it will write information about your application to the
            registry. This information is then used to uninstall or reinstall.
            [color=blue]
            > XML is good for settings which are not good hardcoded in the program however
            > have to be set by instance in advance. What is a XML file more than a new
            > way of the INI file, from which is so often writen that there was a new
            > successor for that, "the registry".
            >[/color]
            XML files are the "newest" and "improved" way of storing configuration data.
            "MOST" of the time all you have to do is make a change to the xml and the
            application will read it once it requires the information. The only time this is
            not true is when the application reads from the configuration file when it
            starts, and stores the information in memory. Then the configuration file may
            not be read until after the application restarts. Remember that, if you want to
            be able to update your app settings (stuff in config file), make sure that you
            read from the config file occasionally to "refresh" your configuration.
            [color=blue]
            > However, just my thought.
            >[/color]
            Of course it is Cor, you are always thinking...wish we could get more from you :D

            jk

            Mythran


            Comment

            • Jonathan Allen

              #7
              Re: If not the registy, then what?

              It is recommended that you store user-specific configuration data in
              either...
              System.Environm ent.SpecialFold er.ApplicationD ata
              System.Environm ent.SpecialFold er.LocalApplica tionData

              The difference is that ApplicationData will follow you from computer to
              computer when you are using a roaming profile in a domain.

              --
              Jonathan Allen


              "SQLScott" <SQLScott@discu ssions.microsof t.com> wrote in message
              news:A50B2370-230B-4DFF-8409-F24420BCD734@mi crosoft.com...[color=blue]
              > In all the books I have read on .Net, they all recommend that using the
              > registry in .net is the "old" way. OK, i'll buy that, but hey don't way[/color]
              what[color=blue]
              > the new way is. Can anyone point me in the right direction?
              >
              > --
              > Thanks,
              >
              > Scott[/color]


              Comment

              Working...