StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14634857
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-01-31T20:48:04.287
FavoriteCount
0
LastActivityDate
2013-02-06T17:09:59.663
LastEditDate
2013-02-06T17:09:59.663
LastEditorUserId
699150
OwnerUserId
699150
ParentId
14409010
PostTypeId
2
Score
7
ViewCount
0
LastEditorDisplayName
text
Body
Ultimately the easiest thing to do is to exclude log4net completely from the ilmerge process and maintain it as a dependent assembly. So after much torture here's the "not-so-obvious" solution.. The excludes were not required after all, the real answer is to use the <code>/lib:[path]</code> switch in ilmerge. I updated the <code>AfterBuild</code> target to remove the excludes from the <code>/internalize</code> switch. Next I added the <code>/lib</code> switch to pass in the location of the log4net dll as a dependent reference. It looks like this: <pre><code><Target Name="AfterBuild"> <CreateItem Include="@(ReferenceCopyLocalPaths)" Condition="'%(Extension)'=='.dll'"> <Output ItemName="AssembliesToMerge" TaskParameter="Include" /> </CreateItem> <Message Text="MERGING: @(AssembliesToMerge->'%(Filename)')" Importance="High" /> <Exec Command="&quot;$(ProgramFiles)\Microsoft\Ilmerge\Ilmerge.exe&quot; /lib:..\packages\log4net.2.0.0\lib\net35-full\ /targetplatform:v2 /log /internalize /keyfile:$(AssemblyOriginatorKeyFile) /out:@(MainAssembly) &quot;@(IntermediateAssembly)&quot; @(AssembliesToMerge->'&quot;%(FullPath)&quot;', ' ')" /> <Delete Files="@(ReferenceCopyLocalPaths->'$(OutDir)%(DestinationSubDirectory)%(Filename)%(Extension)')" /> </Target> </code></pre> In addition, I've added another target to restrict the list of assemblies included in the merge by adding a unique <code><ILMerge /></code> element to the references located in my .csproj file <pre><code><Target Name="AfterResolveReferences"> <Message Text="Filtering out ILMerge assemblies from ReferenceCopyLocalPaths..." Importance="High" /> <ItemGroup> <ReferenceCopyLocalPaths Remove="@(ReferenceCopyLocalPaths)" Condition="'%(ReferenceCopyLocalPaths.ILMerge)'=='false'" /> </ItemGroup> </Target> </code></pre> Thus the reference elements were listed like so to accommodate: <pre><code>... <Reference Include="Ionic.Zip"> <HintPath>..\packages\DotNetZip.1.9.1.8\lib\net20\Ionic.Zip.dll</HintPath> <ILMerge>True</ILMerge> </Reference> <Reference Include="log4net"> <HintPath>..\packages\log4net.2.0.0\lib\net35-full\log4net.dll</HintPath> <ILMerge>False</ILMerge> ... </code></pre> There's probably a better (programmatic) alternative for explicitly adding ILMerge=False values to the <code>/lib</code> switch but, in my case it is sufficient due to there being only one excluded item. Otherwise you may need to add additional paths manually. Credit for the 'AfterResolveReferences' technique I've listed goes to <a href="http://www.hanselman.com/blog/MixingLanguagesInASingleAssemblyInVisualStudioSeamlesslyWithILMergeAndMSBuild.aspx" rel="noreferrer">http://www.hanselman.com/blog/MixingLanguagesInASingleAssemblyInVisualStudioSeamlesslyWithILMergeAndMSBuild.aspx</a> Hopefully this helps someone! 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUsing ILMerge with log4net is causing "inaccessible due to protection level" error
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USNickSuperb
UserOwnerUserId
1. USNickSuperb
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POUsing ILMerge with log4net is causing "inaccessible due to protection level" error
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. CO+1 Thanks for posting the answer to your own question!
 singulars
 PostPostId
 PO
 UserUserId
 USJDB

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.