Saturday, February 25, 2012

Deploy to production using Configuration Properties

Hi,

When you check out the project properties of a RS project, you can find the deployment attributes like targetdatasourcefolder, etc... There's also a button "Configuration Manager...". Here I can see a column "Platform" which is empty. I got the feeling I should be able to configure different platforms here, select an active environment and deploy to it some how. Is this correct; how does this work, and why not?

Regards, Jeroen

The Platform thing is not what you're looking for (it's like different CPU types). It doesn't really apply to what you want to do, it's for compilation purposes.

You deploy to different servers by creating different named configurations (Debug, Production, etc) and setting different target servers for those configurations.

In the Configuration Manager you "attach" one of those named configurations for your report project to one or more configuration setups for the solution as a whole and specifying whether the report project should be build and/or deployed as part of the build process for that solution configuration.

In the Configuration Manager, you also specify one configuration for the solution as "active" so that when you choose to build that is the set of instructions should be used.

When you choose to build and/or deploy specifically for a your report project, rather than for the full solution, I think that the server you have specified in the currently-active configuration settings in Configuration Manager still apply.

I hope that makes sense <g>.

>L<

No comments:

Post a Comment