ssc456
Fully Optimized
- Messages
- 4,280
So regular users of Visual Studio will know that MS for some strange reason decided to stop their native Setup project which builds a lovely MSI package that I always liked.
The alternative they recommend is Installshield LE which I don't like but I've been using it.
Now every other build it seems to forget about half of my DLL files that need to be packaged with it.
my Setup file should be around 25mb, but if I build it then run it on another machine and then need to make a change to build another setup file it will build it and it will only be like 15mb and if I ship it to another PC to install it fails.
I've tried cleaning, rebuilding no luck. The only way I can get it to pick up the DLLs again is to completely kill Visual Studio and re-open it?
It's almost like the first time I build the setup file it forgets to let go of the DLLs so the next time I try it can't copy them over again because the old process of the setup is locking them?
The alternative they recommend is Installshield LE which I don't like but I've been using it.
Now every other build it seems to forget about half of my DLL files that need to be packaged with it.
my Setup file should be around 25mb, but if I build it then run it on another machine and then need to make a change to build another setup file it will build it and it will only be like 15mb and if I ship it to another PC to install it fails.
I've tried cleaning, rebuilding no luck. The only way I can get it to pick up the DLLs again is to completely kill Visual Studio and re-open it?
It's almost like the first time I build the setup file it forgets to let go of the DLLs so the next time I try it can't copy them over again because the old process of the setup is locking them?
