I just released a new version of DVM, 0.3.0. Now with support for Windows :), thanks to Nick Sabalausky. For installation instructions see: https://bitbucket.org/doob/dvm
Changelog:

Version 0.3.0
  New/Change Features
   * Added an option for installing the latest compiler
   * Better compatibility between different shell implementations
   * Added Windows support. Thanks to Nick Sabalausky
   * Added a "list" command for listing installed compilers
   * Added a "uninstall" command for uninstalling compilers

  Bugs Fixed
   * Can't link using DMD 1.068.
   * Issue 2: The '.dvm/bin/dmd-{ver}' scripts don't work on Ubuntu 10.04
   * Issue 7: No error on invalid command
   * Issue 13: Tmp dir should be deleted before running DVM binary (not just after)
   * Issue 5: Invalid character in .dvm/env files
   * Issue 12: "dvm -h" and "dvm --help" print nothing


Upgrading from 0.2.0 to 0.3.0:

It might be necessary to do a complete clean installation by removing ~/.dvm. This is in particular if you had any problems with the previous shell scripts not working.

-- 
/Jacob Carlborg

On 7/17/2011 4:10 PM, Jacob Carlborg wrote:
> I just released a new version of DVM, 0.3.0. Now with support for
> Windows :), thanks to Nick Sabalausky. For installation instructions
> see: https://bitbucket.org/doob/dvm

Awesome news. However, I wasn't able to install without admin. Trying to install as a regular using on Win 7 x64 told me:

An error occurred: Registry Key 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment': Couldn't open key: Access is denied.

As admin it installed successfully.

"Jacob Carlborg" <doob@me.com> wrote in message news:ivvftq$2fvd$1@digitalmars.com...
>I just released a new version of DVM, 0.3.0. Now with support for Windows :), thanks to Nick Sabalausky. For installation instructions see: https://bitbucket.org/doob/dvm
> Changelog:
>
> Version 0.3.0
>   New/Change Features
>    * Added an option for installing the latest compiler
>    * Better compatibility between different shell implementations
>    * Added Windows support. Thanks to Nick Sabalausky
>    * Added a "list" command for listing installed compilers
>    * Added a "uninstall" command for uninstalling compilers
>
>   Bugs Fixed
>    * Can't link using DMD 1.068.
>    * Issue 2: The '.dvm/bin/dmd-{ver}' scripts don't work on Ubuntu 10.04
>    * Issue 7: No error on invalid command
>    * Issue 13: Tmp dir should be deleted before running DVM binary (not
> just after)
>    * Issue 5: Invalid character in .dvm/env files
>    * Issue 12: "dvm -h" and "dvm --help" print nothing
>
>
> Upgrading from 0.2.0 to 0.3.0:
>
> It might be necessary to do a complete clean installation by removing ~/.dvm.

And also by removing the DVM stuff that was auto-added to .bashrc (if any).

> This is in particular if you had any problems with the previous shell scripts not working.
>

If you haven't had such problems, then you should be good without wiping ~/.dvm. The most likely problem was with invoking a specific version of DMD directly via "dvm-{version}", so that should be a good test. (At least that was my experience on Kubuntu 10.04, YMMV.)

This issue shouldn't affect people who used the Windows betas since Windows already uses completely different scripts with completely different syntax.

"Johann MacDonagh" <johann.macdonagh.no@spam.gmail.com> wrote in message news:ivvhtr$2j94$1@digitalmars.com...
> On 7/17/2011 4:10 PM, Jacob Carlborg wrote:
>> I just released a new version of DVM, 0.3.0. Now with support for Windows :), thanks to Nick Sabalausky. For installation instructions see: https://bitbucket.org/doob/dvm
>
> Awesome news. However, I wasn't able to install without admin. Trying to install as a regular using on Win 7 x64 told me:
>
> An error occurred: Registry Key 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment': Couldn't open key: Access is denied.
>
> As admin it installed successfully.

Damn, that's my fault. I thought the try/catch I used would handle that, and I didn't have a restricted account to test with. I guess Windows isn't nice enough to give me a simple exception for that and just bails instead (Or maybe I just caught the wrong exception). I'll fix and submit a pull request.

Couple questions:

- Did you get that after it prompted you for a "yes/no", or did it not get that far?

- Was that message displayed in the cmd prompt or in a dialog box?

On 7/18/2011 5:10 AM, Jacob Carlborg wrote:
> I just released a new version of DVM, 0.3.0. Now with support for
> Windows :), thanks to Nick Sabalausky. For installation instructions
> see: https://bitbucket.org/doob/dvm

The project page still says "Currently no Windows version" under the "Limitations" heading.

On 2011-07-18 06:51, Mike Parker wrote:
> On 7/18/2011 5:10 AM, Jacob Carlborg wrote:
>> I just released a new version of DVM, 0.3.0. Now with support for
>> Windows :), thanks to Nick Sabalausky. For installation instructions
>> see: https://bitbucket.org/doob/dvm
>
> The project page still says "Currently no Windows version" under the
> "Limitations" heading.

Good point, fixed.

-- 
/Jacob Carlborg

On 2011-07-18 00:34, Nick Sabalausky wrote:
> "Jacob Carlborg"<doob@me.com>  wrote in message
> news:ivvftq$2fvd$1@digitalmars.com...
>> I just released a new version of DVM, 0.3.0. Now with support for Windows
>> :), thanks to Nick Sabalausky. For installation instructions see:
>> https://bitbucket.org/doob/dvm
>> Changelog:
>>
>> Version 0.3.0
>>    New/Change Features
>>     * Added an option for installing the latest compiler
>>     * Better compatibility between different shell implementations
>>     * Added Windows support. Thanks to Nick Sabalausky
>>     * Added a "list" command for listing installed compilers
>>     * Added a "uninstall" command for uninstalling compilers
>>
>>    Bugs Fixed
>>     * Can't link using DMD 1.068.
>>     * Issue 2: The '.dvm/bin/dmd-{ver}' scripts don't work on Ubuntu 10.04
>>     * Issue 7: No error on invalid command
>>     * Issue 13: Tmp dir should be deleted before running DVM binary (not
>> just after)
>>     * Issue 5: Invalid character in .dvm/env files
>>     * Issue 12: "dvm -h" and "dvm --help" print nothing
>>
>>
>> Upgrading from 0.2.0 to 0.3.0:
>>
>> It might be necessary to do a complete clean installation by removing
>> ~/.dvm.
>
> And also by removing the DVM stuff that was auto-added to .bashrc (if any).
>
>> This is in particular if you had any problems with the previous shell
>> scripts not working.
>>
>
> If you haven't had such problems, then you should be good without wiping
> ~/.dvm. The most likely problem was with invoking a specific version of DMD
> directly via "dvm-{version}", so that should be a good test. (At least that
> was my experience on Kubuntu 10.04, YMMV.)
>
> This issue shouldn't affect people who used the Windows betas since Windows
> already uses completely different scripts with completely different syntax.

That's correct.

-- 
/Jacob Carlborg

On Sun, 17 Jul 2011 22:10:39 +0200, Jacob Carlborg wrote:

> I just released a new version of DVM, 0.3.0. Now with support for Windows :), thanks to Nick Sabalausky. For installation instructions see: https://bitbucket.org/doob/dvm

Cool!  This is a great tool, very useful.

-Lars

On 2011-07-18 11:31, Lars T. Kyllingstad wrote:
> On Sun, 17 Jul 2011 22:10:39 +0200, Jacob Carlborg wrote:
>
>> I just released a new version of DVM, 0.3.0. Now with support for
>> Windows :), thanks to Nick Sabalausky. For installation instructions
>> see: https://bitbucket.org/doob/dvm
>
> Cool!  This is a great tool, very useful.
>
> -Lars

Thanks.

-- 
/Jacob Carlborg

On 7/17/2011 6:41 PM, Nick Sabalausky wrote:
> "Johann MacDonagh"<johann.macdonagh.no@spam.gmail.com>  wrote in message
> news:ivvhtr$2j94$1@digitalmars.com...
> - Did you get that after it prompted you for a "yes/no", or did it not get
> that far?
>
> - Was that message displayed in the cmd prompt or in a dialog box?

No prompt at all, and it was in the console window.

You can always create a restricted account for yourself to test it out. It will fire if you try dvm-installer.exe install dvm on a machine that already has dvm installed.