By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,572 Members | 1,516 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,572 IT Pros & Developers. It's quick & easy.

Unneeded references

P: n/a
Hi,

Is there a way to detemine which references in a VB.Net project are no
longer required? The compiler doesn't seem to do this - it just copies all
the references to the assembly's manifest.

The only way I have found so far is to remove each reference in turn and
attempt a recompile. If it compiles OK, the reference was obviously
unneeded.

Thanks.
Nov 20 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
* Sheila Jones <sh****************@btopenworld.com> scripsit:
Is there a way to detemine which references in a VB.Net project are no
longer required? The compiler doesn't seem to do this - it just copies all
the references to the assembly's manifest.


There is no direct way to do that. AFAIK, in .NET 2.0, only references
are added to the assembly's manifest if they are needed.

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>
Nov 20 '05 #2

P: n/a
One way could be to remove the references one by one, compile and then check
for errors, no errors, then remove reference

--

OHM ( Terry Burns )
. . . One-Handed-Man . . .

Time flies when you don't know what you're doing

"Sheila Jones" <sh****************@btopenworld.com> wrote in message
news:uL****************@tk2msftngp13.phx.gbl...
Hi,

Is there a way to detemine which references in a VB.Net project are no
longer required? The compiler doesn't seem to do this - it just copies all the references to the assembly's manifest.

The only way I have found so far is to remove each reference in turn and
attempt a recompile. If it compiles OK, the reference was obviously
unneeded.

Thanks.

Nov 20 '05 #3

P: n/a
> Is there a way to detemine which references in a VB.Net project are no
longer required? The compiler doesn't seem to do this - it just copies all


Although this doesn't help you now, In VS2005, there is an option in the
project property pages to list the unused refereces and a button to remove
them.
--
Chris

dunawayc[AT]sbcglobal_lunchmeat_[DOT]net

To send me an E-mail, remove the "[", "]", underscores ,lunchmeat, and
replace certain words in my E-Mail address.
Nov 20 '05 #4

P: n/a
VS2005 Rocks !

--

OHM ( Terry Burns )
. . . One-Handed-Man . . .

Time flies when you don't know what you're doing

"Chris Dunaway" <"dunawayc[[at]_lunchmeat_sbcglobal[dot]]net"> wrote in
message news:4a******************************@40tude.net.. .
Is there a way to detemine which references in a VB.Net project are no
longer required? The compiler doesn't seem to do this - it just copies
all
Although this doesn't help you now, In VS2005, there is an option in the
project property pages to list the unused refereces and a button to remove
them.
--
Chris

dunawayc[AT]sbcglobal_lunchmeat_[DOT]net

To send me an E-mail, remove the "[", "]", underscores ,lunchmeat, and
replace certain words in my E-Mail address.

Nov 20 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.