Spurious dependencies?

[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

 

[James Hahn]

By "refreshing" do you mean Project Properties / References / Unused
Referenences / Remove?

 

[Dale Atkin]

By "refreshing" do you mean Project Properties / References / Unused
Referenences / Remove?

Nope (I meant right click on the setup project and tell it to refresh
dependencies).

I'll try that tomorrow, and see if it helps. Thanks!

Dale

 

[Cor Ligthert[MVP]]

Dale,

You are writing here about a setup and deployment or something else?

Cor

 

[Dale Atkin]

By "refreshing" do you mean Project Properties / References / Unused

Referenences / Remove?

It worked. Thanks a bunch. Still struggling to learn the IDE.

Dale

 

[James Hahn]

Thanks for letting us know that you got it sorted out.