You do not need to add the extension in the AddReference call.
Just clr.AddReference("DotNet4Class")
>From DotNet4Class import *
--
Message: 1
Date: Tue, 6 Nov 2012 19:08:59 + (UTC)
From: Anneka Boccio
To: pythondotnet@pytho
Hi,
I'm using my own python .NET 4.0 build and I'm trying to access some extension
methods for a concurrent queue.
However, the console only shows methods and not extension methods. In visual
studio 2010 C# .NET 4.0, I can see all the extension methods in the
Intellisense/Autocomplete options.
, I use IronPython but I generally
just write what I need in C# and then call it in pythonnet
Thanks for the help!
From: Liam Corrigan
Sent: March-22-12 5:09 PM
To: [email protected]
Subject: RE: import clr_2, import clr_4 vs import clr
I make a reference to System, I need to do it th
So I figured if I had a 'import clr_2',
Then the call to 'clr_2.AddReference("System") would call the 2.0
version of System.
From: Tribble, Brett [mailto:[email protected]]
Sent: March-22-12 4:59 PM
To: Liam Corrigan; [email protected]
Subject: RE: import c
Friedman [mailto:[email protected]]
Sent: March-22-12 5:00 PM
To: Liam Corrigan
Cc:
Subject: Re: [Python.NET] import clr_2, import clr_4 vs import clr
Silly question: isn't a .net 2.0 assembly backwards compatible with a .net 4.0
runtime? Why do you actually need to run a physically sep
port clr_2
import clr_4
clr_2.AddReference("MyDOTNET_2.0_BasedLib")
clr_4.AddReference("MyDOTNET_4.0_BasedLib")
Are there any settings in the source build that I can do, to kick out
two separate clr.pyd and Python.Runtime.dll's with new names and
matching
