April 8, 2010 at 4:29 pm
I would like to know what difference does it make when i select the configuration as debug or debuglocal or production? Does it update any config. related detail? Please help me understand.
[font="Arial"]BASKAR BV
http://geekswithblogs.net/baskibv/Default.aspx
In life, as in football, you won’t go far unless you know where the goalposts are.[/font]
April 9, 2010 at 12:47 pm
If I understand correctly, it can make all the difference or no difference at all. Each option has its own deploy destination. If you set up each option with different configuration settings (different destination server, path, etc.) then when you select an option and then deploy it will deploy to the selected destination. If however, you work in a small environment and don't really have practical options for alternate deployment for testing or whatever, or if you are just lazy and don't bother configuring all the options it doesn't make a difference either.
April 10, 2010 at 2:04 pm
But.. still i can select debuglocal and set the destination server to my test server and the report will get still deployed. Isn't it?
How debuglocal, debug tied up with serverlocation or serverurl?
Please clarify.
[font="Arial"]BASKAR BV
http://geekswithblogs.net/baskibv/Default.aspx
In life, as in football, you won’t go far unless you know where the goalposts are.[/font]
April 12, 2010 at 9:29 am
I think they are just names that many people would commonly use. But in reality they could be DeployA, DeployB, and DeployC. So yes, you could choose Production and configure it to deploy locally or some other odd variation. The names do not really restrict you from where you can configure the deployment destination, the names are more guidelines to help you keep things straight in your head.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply