InfoPath Dev

I am getting ready to publish an infopath form, the process in my development environment has been to (within the publish wizard) publish to a sharepoint server specifying a server with infopath services on my dev network and enable for browser usage as an admin approved template which gives me an xsn that I use to deploy from central administrator.  I have a couple of concerns about this because I will be publishing to different servers during the testing/deployment process, so:

 1) During the publish process it asks for the target site name "Enter the location of your SharePoint or InfoPath Forms Services site" -- will it behave if I try to deploy the form to a site with a different server name?  (i.e. I create the xsn on my dev network using http://dev/ but will it deploy properly to one of the test servers that may have a different name such as http://test/)

2) I am using a Contact Selector control in my form, this requires the Context.xml file that has the name of the target sharepoint server -- it doesn't seem to matter what the name of the server actually is, I switched it to http://test/ and used it on my dev network and it still worked fine.. just a little concerned, maybe nothing to worry about?

 Thanks for any clarification.

Hi - I'm pretty sure for item 1 that you'll need to republish the template to specify the server you intend to upload it to. You may simply want to check that - put in http://test/ when you publish, and try to upload to http://dev/

As to question 2, the Context.xml is used by the contact selector when previewing the form - once published to SharePoint, it woun't be used.

Well the issue with publishing to /test/ when I'm in my dev environment is that I'll get an error saying the specified server does not exist.  I was thinking I might do something like set up /test/ within my dev network, but I have more than one place I'm deploying to, one is a staging environment and one is production, neither have the same server name.  I am also concerned that it may be interacting with the database attached to that server in some manner.. so even if it had the same name it would misbehave if I took it to another server..  I will be finding a lot of this out the hard way very soon!