Setup Project Headaches
-
I have noticed that Visual Studio .Net 2003 enjoys automatically adding dependencies to the setup project that cause the build to fail unless they are excluded. (ex. msado27.tlb, msado26.tlb, activeds.tlb, etc.) I am trying to build a large number of applications at once using a script which is not a problem when testing the script on my machine since it is the development machine and I have already excluded the "bad" files. The problem pops up when I try to build the applications on a different machine where Visual Studio believes that it should add different dependencies and therefore fail during the building of the setup project. :mad: I have yet to see the use of requiring a file that must be excluded. :confused: Is there anyway to exclude files before they show up as dependencies? Like a list of files that if they show up, they are excluded? Or maybe a filter of some sort.... "Don't include *.tlb" :Hopeful: Thanks -J
Think of a computer program. Somewhere, there is one key instruction, and everything else is just functions calling themselves, or brackets billowing out endlessly through an infinite address space. What happens when the brackets collapse? Where's the final 'end if'? Is any of this making sense? -Ford Prefect
-
I have noticed that Visual Studio .Net 2003 enjoys automatically adding dependencies to the setup project that cause the build to fail unless they are excluded. (ex. msado27.tlb, msado26.tlb, activeds.tlb, etc.) I am trying to build a large number of applications at once using a script which is not a problem when testing the script on my machine since it is the development machine and I have already excluded the "bad" files. The problem pops up when I try to build the applications on a different machine where Visual Studio believes that it should add different dependencies and therefore fail during the building of the setup project. :mad: I have yet to see the use of requiring a file that must be excluded. :confused: Is there anyway to exclude files before they show up as dependencies? Like a list of files that if they show up, they are excluded? Or maybe a filter of some sort.... "Don't include *.tlb" :Hopeful: Thanks -J
Think of a computer program. Somewhere, there is one key instruction, and everything else is just functions calling themselves, or brackets billowing out endlessly through an infinite address space. What happens when the brackets collapse? Where's the final 'end if'? Is any of this making sense? -Ford Prefect
I personally stopped using VS.NET 2003 for Setup Project. I took the time to write one batch installer, which is included with my ZIP-file and will install the directory to any location desired and make changes to the registry. If you are not programming for profit, you might want to look into Nullsoft Installer or other "free for non-commercial use"-setup tools, which usually wield a much bigger palette of tools than the castrated "Windows Install Maker" included with VS.NET 2003 Cheers, Sebastian -- Contra vim mortem non est medicamen in hortem.
-
I personally stopped using VS.NET 2003 for Setup Project. I took the time to write one batch installer, which is included with my ZIP-file and will install the directory to any location desired and make changes to the registry. If you are not programming for profit, you might want to look into Nullsoft Installer or other "free for non-commercial use"-setup tools, which usually wield a much bigger palette of tools than the castrated "Windows Install Maker" included with VS.NET 2003 Cheers, Sebastian -- Contra vim mortem non est medicamen in hortem.
I appreciate the answer, but changing our installer is, unfortunately, not something we can do. Thanks -J
Think of a computer program. Somewhere, there is one key instruction, and everything else is just functions calling themselves, or brackets billowing out endlessly through an infinite address space. What happens when the brackets collapse? Where's the final 'end if'? Is any of this making sense? -Ford Prefect