Well, if you use connection strings which are embedded in the config file, you could list all three possible connectionstrings and load the appropriate one in each environment.
It is also a common design decision to construct connection strings based on parameters supplied from a common database server. (the connection to *that* database would be available freely within the intranet or based on domain accounts). On Jul 28, 6:26 pm, Molleri F´ <[email protected]> wrote: > I'm starting to develop a project that will share in both desktop and > web use in 3 environments: > development, approval and production. What would be the best way to > structure this project in visual studio to work? > how I can organize the different connection strings for each scene in > time to make the deployment of the application? > I can do this with the same solution, or I need three versions of a > solution for each environment? > I will use this project with the svn for version control. > now thanks.
