#1393 closed defect (fixed)
Maestro does not launch from installer
| Reported by: | andrewd | Owned by: | jng |
|---|---|---|---|
| Priority: | low | Milestone: | Maestro-3.0 |
| Component: | Maestro | Version: | 2.1.0 |
| Severity: | trivial | Keywords: | |
| Cc: | External ID: |
Description
Ever since the 2.1 betas, the installer fails to launch Maestro after install (for me, anyway). I can run it just fine normally, but the installer has a checkbox that is checked by default which says it will launch Maestro....this doesn't seem to work. I'm running Windows 7 x64. This worked in 2.0 and prior...I'd thought that I'd submitted this bug during the betas, but apparently I forgot to - sorry!
Change History (5)
comment:1 by , 14 years ago
| Milestone: | → Maestro-2.x |
|---|
comment:2 by , 14 years ago
comment:3 by , 14 years ago
The problem was that the path to ConnectionProviders.xml was sensitive to the working directory. When you normally launch Maestro from the start menu shortcut the working directory is the directory where Maestro is installed.
When you launch Maestro from the installer finish screen, the working directory is the directory where you ran the installer, hence the ConnectionProvider.xml file could be found. Wix (the toolkit used to build the installer) doesn't have a mechanism to set the working directory when launching Maestro after installation.
I've fixed the logic used to find this file in r5030
comment:4 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
An update - I've tried to install this on an XP Pro virtual machine, and on Windows Server 2008 x64. In both cases, it launched automatically after install...so it is maybe just something that happens with Windows 7 x64?
Another thing to note though - on both of those other boxes, when it ran the first time and I tried to log in, it threw an error saying that it couldn't find my providers xml file (which it was trying to find on my desktop, for some reason). If I closed the program and opened it again, it no longer had that error. Though, thanks to this elusive ticket 1370 http://trac.osgeo.org/mapguide/ticket/1370, I still can't log in on any other these boxes using 2.1.