Обсуждение: 'Stealing' SQL files association considered harmful
Testing pgAdmin III 1.7.0 (6292:6293) on Windows XP. After I installed it the SQL files (.sql) were associated with it. They used to be associated with my default editor. When I tried to delete the new association I could not find the extension in the "File Types" list (Windows Explorer > Tools > Folder Options). So I had to open the registry and delete the association from there. So if that feature will be in 1.8 I would like to request an option in the installer for it. -- Milen A. Radev
Milen A. Radev wrote: > Testing pgAdmin III 1.7.0 (6292:6293) on Windows XP. After I installed > it the SQL files (.sql) were associated with it. They used to be > associated with my default editor. When I tried to delete the new > association I could not find the extension in the "File Types" list > (Windows Explorer > Tools > Folder Options). So I had to open the > registry and delete the association from there. > > > So if that feature will be in 1.8 I would like to request an option in > the installer for it. > I've spent a couple of hours researching this and I can't see how this can be achieved in wix without manually re-authoring all the dialogues and adding a custom action (which would be a *lot* of work). The way we're adding the association is exactly per Wix/MS's spec. Trying to move it into a seperate feature so it can be disabled causes the database to fail it's ICE69 validation check because it needs to be in the same feature as it's target. Ideas anyone? Magnus? Regards, Dave.
Dave Page wrote: > Milen A. Radev wrote: >> Testing pgAdmin III 1.7.0 (6292:6293) on Windows XP. After I installed >> it the SQL files (.sql) were associated with it. They used to be >> associated with my default editor. When I tried to delete the new >> association I could not find the extension in the "File Types" list >> (Windows Explorer > Tools > Folder Options). So I had to open the >> registry and delete the association from there. >> >> >> So if that feature will be in 1.8 I would like to request an option in >> the installer for it. >> > > I've spent a couple of hours researching this and I can't see how this > can be achieved in wix without manually re-authoring all the dialogues > and adding a custom action (which would be a *lot* of work). > > The way we're adding the association is exactly per Wix/MS's spec. > Trying to move it into a seperate feature so it can be disabled causes > the database to fail it's ICE69 validation check because it needs to be > in the same feature as it's target. > > Ideas anyone? Magnus? Not really. I would've suggested the separate feature thing, but if that doesn't work... Can we make it a checkbox and disable it from there? //Magnus
Magnus Hagander wrote: > Not really. I would've suggested the separate feature thing, but if that > doesn't work... > > Can we make it a checkbox and disable it from there? That's what would require a CA and custom dialogs. The CA because there is no way to put a condition on the appropriate tags, and custom dialogues because at the moment we're using the stock WiX ones and we'd need a whole set to replace them to add just one custom one. :-( /D
Dave Page wrote: > Magnus Hagander wrote: >> Not really. I would've suggested the separate feature thing, but if that >> doesn't work... >> >> Can we make it a checkbox and disable it from there? > > That's what would require a CA and custom dialogs. The CA because there > is no way to put a condition on the appropriate tags, and custom > dialogues because at the moment we're using the stock WiX ones and we'd > need a whole set to replace them to add just one custom one. Maybe pgAdmin3 could ask upon first startup whether you want it to associate .sql files with itself or not? And maybe a button in the preferences window "Assign Now" for those who later change their opinion? greetings, Florian Pflug