Menu

#30 User-defined Database Folder

2.10.19
closed
None
5
2015-02-27
2015-01-27
Rado
No

I've been using user-defined database folder to not mess my settings (specifically groups) with other administrators' settings.

It would be perfect if installation program remembers folder I chose in previous installation.

Related

Feature Requests: #30

Discussion

  • R. Hoek

    R. Hoek - 2015-02-16

    You can specify the default storage location during installation, but this does not work for me to:
    1) because WOL uninstalls WOl during installation, the location is 'removed' from the setting (as far as I noticed)
    2) I use a different filename, then the one used bij WOl

    This setting is available insite the setting config file located at 'C:\Users\187rh\AppData\Local\Aquila_Technology\WakeOnLan.exe_Url_jzwizg205esfc3x12c52lpq14ldbgr5k\<app version>'

    Can you adjust this setting, so the 'user.config' is located just one folder higer? This way I will be accessable between the different versions...

    Of course you'll need to take config migrations in account.

     
  • BasilDane

    BasilDane - 2015-02-16

    I have been looking at this.
    It's not easy to move user.config. This particular file is owned and managed by DotNet. I do not set it's location. Can you explain more about what is wrong here? This file is control by the Microsoft components and I don't see any cases where it would not be accessible. Feel free to email me directly Ron. Thanks.

     
    • Rado

      Rado - 2015-02-17

      I should said that I'm talking about machine.xml. Because it's better once to see than 3 times to hear ;) I captured a couple of screenshots during last upgrade.

      First screenshot demonstrates my current location of machine.xml, but installattion program always set path to database (i.e. machine.xml) to default path (c:\ProgramData\Aquila...) ignoring my selection from previuos installation (c:\users\xxx\Documents\Aquila...). I have to always change it manually.

       

      Last edit: Rado 2015-02-17
    • R. Hoek

      R. Hoek - 2015-02-17

      Hello Phil,

      I'm not sure how the Microsoft installer Works (we don't use it). But the problem is, that for some reason the original config file is not correctly 'copied/moved/applied' to the new version path...
      When I start the application it looks like it 'partially' copies the config from the old location... But I can't exactly grasp what going wrong....

      To test it, I did the following:

      · Installed version 2.10.017

      o Started application (interface is 'English' by default - not based on system)

      o Set my DB location to some complete other path (ex. H:\MyMachines.xml)

      o Selected Dutch language

      o Folders/files created

      § C:\ProgramData\Aquila Technology\WakeOnLan\2.10.17.0

      § %userprofile%\AppData\Local\Aquila_Technology\WakeOnLan.exe_Url_jzwizg205esfc3x12c52lpq14ldbgr5k\2.10.17.0\user.config

      · Installed version 2.10.18-20

      o Did NOT start it yet

      o No new folders yet at

      § C:\ProgramData\Aquila Technology\WakeOnLan

      § %userprofile%\AppData\Local\Aquila_Technology\WakeOnLan.exe_Url_jzwizg205esfc3x12c52lpq14ldbgr5k

      · Started new version

      o Interface is now again 'English'

      o Open the 'settings'

      § Language is now automaticly set tot 'dutch' ??

      § DB location is 'C:\ProgramData\Aquila Technology\WakeOnLAN\machines.xml'
      Regards,
      Ronald Hoek
      Application Developer
      ComponentAgroB.V.
      Oud-Beijerland - The Netherlands
      Website: http://www.componentagro.nl
      KvK: H24264020
      Van: BasilDane [mailto:basildane@users.sf.net]
      Verzonden: maandag 16 februari 2015 17:34
      Aan: [aquilawol:feature-requests]
      Onderwerp: [aquilawol:feature-requests] #30 User-defined Database Folder

      I have been looking at this.
      It's not easy to move user.config. This particular file is owned and managed by DotNet. I do not set it's location. Can you explain more about what is wrong here? This file is control by the Microsoft components and I don't see any cases where it would not be accessible. Feel free to email me directly Ron. Thanks.


      [feature-requests:#30]http://sourceforge.net/p/aquilawol/feature-requests/30 User-defined Database Folder

      Status: open
      Milestone: Pending
      Created: Tue Jan 27, 2015 04:56 PM UTC by Rado
      Last Updated: Mon Feb 16, 2015 09:23 AM UTC
      Owner: nobody

      I've been using user-defined database folder to not mess my settings (specifically groups) with other administrators' settings.

      It would be perfect if installation program remembers folder I chose in previous installation.


      Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/aquilawol/feature-requests/30/https://sourceforge.net/p/aquilawol/feature-requests/30

      To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/https://sourceforge.net/auth/subscriptions

       

      Related

      Feature Requests: #30

  • BasilDane

    BasilDane - 2015-02-18

    First, apologies for this problem.

    Here is what's happening. We use Installshield for the installer. The free version.
    To make this work correctly, we should be doing "upgrades", not "full installs". That way Installshield would preserve your previous selection.

    The problem is: Installshield-Free does not support upgrades.
    They want us to pay for professional edition. And it is ridiculously expensive.

    I have no problem switching over to different install platform, but it's going to be a large task to support DotNet.

    I'm open to suggestions.

    One possible solution would be to remove this option from the installer, and instead give you the option to move it inside the WOL program. Then WOL would have full control over the whole matter.

     
  • R. Hoek

    R. Hoek - 2015-02-19

    Let's skip the Microsoft cursing en continue to the solution ;)

    Regarding the first option: We use Inno Setup for our installation management. It does not come with native .NET support, but has a large community which can help you with this. There's a 32-bit and 64-bit installer available.

    Second: putting the config-file outside the .NET/Windows Installer management is also a good idea. I would put 'user.config' in the 'Roaming' userprofile location (Ex. %userprofile%\AppData\Roaming\Aquila_Technology\WakeOnLan\user.config) and set machines.xml location to the same folder by default.
    The user can change it the same way they do now, but the config is always in the same spot.
    To get the roaming data path without the version suffix use 'Path.GetDirectoryName(Application.UserAppDataPath)'

     
  • BasilDane

    BasilDane - 2015-02-20

    One step at a time here, I'm pleased to announce that I have the machines.xml path issue sorted out in Installshield.

    Please see Beta 30.
    https://sourceforge.net/projects/aquilawol/files/Beta/

    The installer is now properly saving your database path between installs. You can even uninstall and reinstall and it will keep your current path setting.

    • You may have to manually set it this time, because your registry doesn't have the correct setting yet.
     
  • BasilDane

    BasilDane - 2015-02-20

    Ron, I do have the ability to save the user.config to the roaming store. I'm looking at this now.

     
    • R. Hoek

      R. Hoek - 2015-02-23

      I took a look at this. I do see the setting 'Database' in the Registry key 'HKEY_CURRENT_USER\Software\Aquila Technology\WakeOnLan'...
      However, I'm missing the actual XML filename, because this is different to the default. Only the directory of the file is saved.

       
  • BasilDane

    BasilDane - 2015-02-23

    That's correct. The registry key you are referring to is only for communication between Installshield and the application.

    The user.config is where all the settings are kept, including the path and name of the database file.

    I have changed my path and filename from the default, and everything is working here.

     
  • R. Hoek

    R. Hoek - 2015-02-23

    Can you create a new 'build' (so InstallShield wont see it as '2.10.18.32'). Then I can test whether the settings persist after updating to a newer version.

     
  • BasilDane

    BasilDane - 2015-02-23

    .35 is up now.

     
  • R. Hoek

    R. Hoek - 2015-02-24

    During install I can see the modified installation path.
    When I start the application, the original database (XML) is loaded and in the options I can see the correct configuration!

    However I do have one small bug (not specific to this build). But I'll make a new issue for that.

     
  • BasilDane

    BasilDane - 2015-02-27
    • status: open --> closed
    • assigned_to: BasilDane
    • Milestone: Pending --> 2.10.19
     

Log in to post a comment.