Ok, gonna vent a bit here. One of my customers uses click-once to deploy apps to their users.
There is nothing more annoying than publishing an app and finding out one of the Applications Files has been set to "Prerequisite" instead of "Include" and get an e-mail with a screen shot of the big error message that says Infragistics controls were not included.
It is pretty much the default behavior of every third party library I reference to set Include as the default. Why, why, why in the world would you have it set to Prerequisite. This setting resets back to the default any time I change my Infragistics references so it regularly makes me look like an idiot who publishes buggy software.
It would be a big help if this could be changed. I know a lot of people don't use click-once, but in some cases it is a necessary evil.
Thanks,
Chris
Dude! This post is like 3 years old!
Chris and Steve,
The default of Prerequisite comes from copy local setting of the reference in the project. By default when you drag a control on the form the reference will have this set to false and as a result the assembly is a prerequisite for click once. There are more details on this in the How to: Specify Which Files Are Published by ClickOnce topic on MSDN.
Let me know if you have any questions.
The same thing has happened to me as well.
One thing I've been considering is creating some kind of install package that includes all the Infragistics controls and set it as a click once prerequisite so that the controls would be installed on the client one time and then that is 20 meg less that needs to be downloaded when I update the software. If I change my references to say a newer version then I would just need to remember to update my control install package as well.
Ultimately the only way to make sure everything works is to have someone test it before full deployment.