StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13714580
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-12-05T00:49:12.197
FavoriteCount
0
LastActivityDate
2016-12-05T23:54:58.833
LastEditDate
2016-12-05T23:54:58.833
LastEditorUserId
292502
OwnerUserId
292502
ParentId
4831815
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
I followed @x0n's instructions but it didn't work out well for me. Maybe I was missing something. I have to admit that I could not load my <code>dll</code>s with <code>ReflectionOnlyLoad</code> because of a COM error. So I loaded them with <code>LoadFile</code>. The assembly references provided by <code>LoadFile</code> was exactly the same when I loaded the Assembly with Reflector. In the end my PowerShell script generated a list showing the references which are in the project but not loaded by the assembly. In theory these supposed to be the "unnecessary" references. When I started to remove them, the build failed. For example in case of my first project the lack of any of the 4 "unnecessary" references would cause the build to fail. I skim through the output of the powershell script and it lists "<code>System</code>" too for example. If I remove it the compiler doesn't even complain about a bunch of "<code>using System;</code>" but it fails before that - stating that I need to reference that assembly because of an interface... BTW, our project is not a toy, it involves 140+ dlls (almost half of which is Test <code>nUnit</code> dll though) and I thought I'll do some houskeeping. My script (which doesn't go recursively into project folders - some projects contain more dlls) so maybe someone can use it: ` $dte = [System.Runtime.InteropServices.Marshal]::GetActiveObject("visualstudio.dte") <pre><code>$binfiles=Get-ChildItem C:\YourSourcePath\bin\debug $dlls=$binfiles | where { $_.extension -eq ".dll" -and $_.name -like "*YourCompanyName*" } foreach ($dll in $dlls) { foreach($prj in $dte.solution.projects) { if ($prj.Kind -eq "{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") { if ($prj.Properties.Item("OutputFileName").Value -eq $dll.Name) { $loaded = [reflection.assembly]::LoadFile($dll.FullName) $refs = $loaded.GetReferencedAssemblies() Write "=============" Write $dll.Name Write "-------------" foreach($pref in $prj.Object.References) { $found = 0 foreach($ref in $refs) { if ($ref.Name -eq $pref.Name) { $found = 1 break; } } if ($found -eq 0) { Write $pref.Name } } } } } } </code></pre> `
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POC#: Automated removal of unnecessary assembly references?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCsaba Toth
UserOwnerUserId
1. USCsaba Toth
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.