I realize this may not work for your situation, but it could provide a workaround until/unless RS implements your proposal. Even though my home office LAN uses DHCP, I set up my Windows XP environment running in Parallels on my iMac with a static address towards the high end of the range of addresses in my LAN's subnet. Now I never have to change the IP address setting for remote debugging in RB. I only have a few network devices on my LAN, so probably any IP address with a fourth octet above 10 would be safe, but I set it to a number in the 200's just to be safe. DHCP should never dole out an address that high to any other device. Of course if you're connecting your MacBook to a much busier LAN, this idea might not be feasible.
On 12/9/06, Joe Huber <[EMAIL PROTECTED]> wrote:
I've submitted a feature request that the remote debug stub be identified by its Name instead of its IP address. You may want to sign on if you debug using a laptop or your network uses DHCP. http://www.realsoftware.com/feedback/viewreport.php?reportid=xhcbetia The main issue is that using a static IP address is a brittle mechanism and easily breaks if the remote host's IP address changes for any reason. If you use Parallels on a MacBook, then RB can't locate the remote stub anytime you move the MacBook to another network. You have to manually tell the IDE to go rediscover and configure the stub. Since the IDE already can discover the stub's name and IP address, my suggestion is that it should automatically do so whenever starting up a new remote debugging session. Or at least when it can't find the stub at its last known IP address.
_______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
