StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2460626
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-03-17T08:01:59.060
FavoriteCount
0
LastActivityDate
2010-03-17T08:11:36.607
LastEditDate
2010-03-17T08:11:36.607
LastEditorUserId
121364
OwnerUserId
121364
ParentId
2460542
PostTypeId
2
Score
8
ViewCount
0
LastEditorDisplayName
text
Body
One solution (or workaround) would be to install both versions in the Global Assembly Cache (GAC) on the machine(s) on which your software needs to run, and reference the assemblies using their strong names. This assumes that the assemblies do indeed have strong names. Installing into the GAC will be a pain if you have more than a few developers or if you plan to deploy your solution to many computers (eg as an end-user application). In this case, I believe (but I might be wrong) that your only option is to merge one of the two versions into the assembly requiring that version. In your specific case, you need <code>Castle.DynamicProxy2.dll</code> v2.1 to be merged into <code>NHibernate.dll</code>. You can use a tool called <a href="http://research.microsoft.com/en-us/people/mbarnett/ilmerge.aspx" rel="noreferrer">ILMerge</a> to merge the assemblies. The command you will need to run looks something like this (untested): <pre><code>ILMerge /t:library /internalize /out:Deploy/NHibernate.dll NHibernate.dll Castle.DynamicProxy2.dll </code></pre> The <code>/internalize</code> switch tells ILMerge to mark all types from the second assembly (Castle in this case) <code>internal</code> in the output assembly. Without this, you might get compile errors when you try to compile a project referencing both your new <code>NHibernate.dll</code> and the shelf version of <code>Castle.DynamicProxy2.dll</code> v2.2, as they will contain classes with the exact same names.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUsing different versions of the same assembly in the same folder
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJørn Schou-Rode
UserOwnerUserId
1. USJørn Schou-Rode
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. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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. 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.