I have a WPF application.. I need to create 3 setups, each setup is for an environment(development, staging and production), I've put each environment configuration into App.config file of my main UI project. I need Installshield to pull the appropriate configuration file while creating the setup file.
A question: Is there a way to do it differently?
thanks,
There are several approaches you could take. Here's one:
In recent versions of InstallShield (Professional and higher editions), you can override Path Variables on a per-Release basis. If you craft your source filesystem and source path correctly, this should let you select from multiple source app.config files just by building a different release.
Related
I would like to be able to publish from visual studio. I am able to do this
I have different configurations for Debug,QA,Release. I am using config transforms and they work fine.
ISSUE: when I publish the I want the Debug, QA,Release to be published to their respective folder example E:\Application\Debug and so on. I am able to do this by changing the Publishing folder location and Installation folder location manually. How can this be such: f I change the configuration these locations are selected automatically. So when I need to publish a particular version -> and all I need to do is
change the config
press the publish now button.
Thanks!
The only possibility I know of would be to use a Build Server and build if the Source code changes (probably seperate branches) and have build definitions for each case.
This would mean that you would have to have a kind of source control (Git, Mercurial, TFS) for the Project and the resources to run that kind of service or use a Service on the internet.
Build Server for local installation:
TeamCity
Team Foundation Server
Build Server via Internet:
VisualStudio.com
(Those are the onse that come to my mind because I have used them before. There are much more available)
With a 2012 SSDT database project and a Integration Services project within it using project deployment model, after a build, a .ispac file is not created for me. Is there a setting or option that is necessary to allow this to be created?
The project builds successfully, and successfully creates the .dacpac file too. Building from the solution or individual project, the .dacpac file is created, and I see both projects are built successfully when built from the solution. I can also successfully create a .SSISDeploymentManifest file too. Of course, the run the all the packages without error as well.
Also, the Non-Default Properties Report shows only MaxConcurrentExecutables and EnableConfigurations for project level properties have non default values.
I feel like there is something small I'm missing. Any help is appreciated.
If a package is converted to use the package deployment model, a .ispac is not created when the project is built. It is only created when the project is using the project deployment model. The answer was in the question the entire time...
What is the best way to upgrade a local development version of DNN source without destroying the database (pages, settings, module settings, etc..)?
I'm currently moving from 07.00.XX to 07.02.00 and there is a tremendous amount of refactoring, seems impossible to just overlay the source.
Is there a way I can do this with preservation of all settings, etc....or will I need to rebuild parts of the site?
Since you are using the SOURCE package, you should be able to simply copy the SOURCE files from the ZIP file you download, over all of the existing files.
You might make sure that the new SOURCE package doesn't have a web.config file, if it does, remove/rename that so that it doesn't replace your existing web.config file, and thus saving your MachineKeys and connection strings.
Back up the FILES and Database before you attempt this however, just to be safe.
After the copy you might have to build the solution before the upgrade will work.
I typically don't recommend using the SOURCE package for DNN, unless you absolutely need to make changes (not recommended) to the source, it isn't necessary for doing Module Development or skinning.
I have two application configuration files in my application directory. One is named Test.config and the other is named MyApp.exe.config.
Test.config is similar to MyApp.exe.config with slight modifications.
If I execute MyApp.exe, it uses Test.config to run as certain aspects of the application is configured within these configuration files. However, if I rename MyApp.exe.config to MyApp1.exe.config, the application will not start.
If I delete Test.config, application launches correctly using settings in MyApp.exe.config. This is a .NET 3.5 WPF application.
Anyone run into this.
TIA.
I've been using SlowCheetah to transform my app.config files and this part is all working fine. The correct transforms are applied to AppName.exe.config when I build the windows client application.
The problem I have is that the S&D Project always looks for app.config which obviously does not contain the updated values.
How can I configure the S&D project to look for AppName.exe.config and package that instead?
After some lengthy research it seems this is not possible when building an MSI using VS 2010 Setup & Deployment.
It may be possible to do with MSBUILD as this is more powerful and flexible but I currently don't have the time to explore that avenue in detail.
So for the time being as a temporary workaround I have entered the values in app.config for the production environment as this is what the MSI will use.
My transforms are still in place for other environments. But seeing as I don't deploy to other environments with MSI it doesn't really matter.
At some stage I will sort this all out with a build server and CI.
Hope this helps someone, someday.