D
Dale Atkin
Somewhere in the development of the program I'm working on, I did something
that a whole bunch of dependencies to be added to my project.
I'm not sure where these extra dependencies came from, but I'd like to
figure out how to 'purge' them from my project so that I don't bloat the
installer. (It went from 800kB --> 8MB). Anyone know of a way I can
determine what is causing VB.NET to decide that a particular file is needed?
I tried refreshing the dependencies, but that didn't work.
I've manually excluded a large number of files from the setup, but that
really isn't the way I should be doing this!
Dale
that a whole bunch of dependencies to be added to my project.
I'm not sure where these extra dependencies came from, but I'd like to
figure out how to 'purge' them from my project so that I don't bloat the
installer. (It went from 800kB --> 8MB). Anyone know of a way I can
determine what is causing VB.NET to decide that a particular file is needed?
I tried refreshing the dependencies, but that didn't work.
I've manually excluded a large number of files from the setup, but that
really isn't the way I should be doing this!
Dale