Is ClickOnce deployment appropriate?

Hi,

I've got an application that I currently wrap in an msi. Everything's fine,
except I'd like to be able to push updates to my users. The update mechanism
of clickonce deployment looks excellent and would be very useful. My
application's installer doesn't touch the GAC or registry, so it seems like a
good cantidate for ClickOnce. However, this application is launched from
another application, and the path to the application is currently hardcoded
in a configuration file (it's dependent on it being installed in the same
location on every machine). I know this isn't very elegant, but it's a
limitation of the other tool. Keeping that in mind, is there a way to know
ahead of time where clickonce will install to? Otherwise, could I somehow
take advantage of the updating mechanism with my current setup?

Thanks...

-Ben