developer.* Blogs - Design Issue With SSIS BIDS Package Configuration Wizard - Comments

If you mean anything like

Edward G Nilges — Sat, 14 Oct 2006 07:31:12 -0700

If you mean anything like the old "setup" for old Visual Basic: the bin folder contains a debug and a release folder. Look in the release folder for an .exe with the name of your application. That is all you need to ship in simple cases as long as the target system has the .Net Framework, which can be downloaded for free at Microsoft.

Setup and installation is remarkably easy as compared to old VB.

how to make setup in vb.net.

nainesh — Sat, 14 Oct 2006 03:55:11 -0700

how to make setup in vb.net.

Wizard behaviour impact on a multiple-package configuration file

David Norman — Tue, 21 Feb 2006 15:10:38 -0800

This DeFeCT (DEsign FEature Considered Tenable) is all the more annoying when using one config file for multiple packages, since subsequent wizard runs wipe out any pre-existing properties in the config file.

If I am to get any benefit from the Wizard's xml generation then I have to take the following steps:

1. Add a new config file for each package
2. Manually merge the files into a global config file, removing any duplicate properties
3. Remove the individual package config files from the packages and add the new global config file
4. Check it all still works

Several iterations of this process are pretty much guaranteed to introduce typos and general hair tearing.

Design Issue With SSIS BIDS Package Configuration Wizard

Daniel Read — Thu, 19 Jan 2006 08:59:43 -0800

Unless I'm totally missing something, I've uncovered a pretty annoying bug design feature in the Package Configuration wizard in BIDS (the SQL Server 2005 Business Intelligence Design Studio). Whenever you walk through the wizard it throws away any values that you've placed in the dtsConfig XML file.