Databases
StackOverflow2013
Postsdbo
PO.NET resolves a class to the wrong DLL
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO.NET resolves a class to the wrong DLL
    primarykey
    data
    text
    <p>My C# project has references to two third party DLLs. This is important because it means I don't have access to source code and can't modify or recompile these two DLLs.</p> <p>Let's call them dll A and dll B. Here's what dll A looks like:</p> <pre><code>namespace ThirdParty.Foo { public class Bar { ...snip... } public class Something { public Bar MyProperty { get; set; } } } </code></pre> <p>And here's what dll B looks like:</p> <pre><code>namespace ThirdParty.Foo { public class Bar { ...snip... } public class SomethingElse { public Bar MyProperty { get; set; } } } </code></pre> <p>As you can see, they have the same namespace and they both define a class with the same name. My C# code needs a reference to both DLLs. I use the alias property on the reference to be able to distinguish between the two references and I also <code>extern alias firstDll</code> and <code>extern alias secondDll</code> at the top of my C# file. So far so good.</p> <p>It seems obvious to me that the type of <code>Something.MyProperty</code> is firstDll.ThirdParty.Foo.Bar and the type of <code>SomethingElse.MyProperty</code> is secondDll.ThirdParty.Foo.Bar but for some reason, Visual Studio gets confused and resolves the type of both properties to the same <code>Bar</code> class in firstDll. </p> <p>Is there a way for me to "force" VisualStudio to resolve the correct type?</p> <p>EDIT: the error I'm getting in Visual Studio is: Cannot implicitly convert type 'ThirdParty.Foo.Bar [d:\MySolution\References\Second.dll]' to 'ThirpParty.Foo.Bar [d:\MySolution\References\First.dll]'</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USdesautelsj
    1. USdesautelsj
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PO.NET resolves a class to the wrong DLL
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO.NET resolves a class to the wrong DLL
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO.NET resolves a class to the wrong DLL
      1. This table or related slice is empty.
      1. VTUpMod
    1. COJust to make sure, you want to distinguish between two types of exactly the same name in exactly the same namespace, but from two different referenced assemblies, correct?
      singulars
      1. PO.NET resolves a class to the wrong DLL
      1. USJan Doerrenhaus
    2. COYou could enumerate all the types from each `Assembly` individually and then instantiate the one you want using `Activator.GetInstance()`. However, this probably won't help at design time.
      singulars
      1. PO.NET resolves a class to the wrong DLL
      1. USMartin Parkin
    3. CO@JanDoerrenhaus yes that's correct and what's important to realize is that these are 3rd party DLLs, I can't recompile or anything. I am just very surprised that VS.NET is not resolving a type to the 'Bar' in the corresponding DLL.
      singulars
      1. PO.NET resolves a class to the wrong DLL
      1. USdesautelsj
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload