OK. Will try and get back to you by Monday :)
Piotr
On Fri, Jan 7, 2011 at 5:02 PM, Dino Viehland wrote:
>
> Piotr wrote:
>> import System. - works
>>
>> import System
>> System. works too. There's no ASCIIEncoding) but there's AppDomain
>> for example and the list starts with AccessViolationEx
Piotr wrote:
> import System. - works
>
> import System
> System. works too. There's no ASCIIEncoding) but there's AppDomain
> for example and the list starts with AccessViolationException and ends with
> {} Web System.Text.ASCIIEncoding does work
>
> but again
> import System.Text
> System. doe
import System. - works
import System
System. works too. There's no ASCIIEncoding) but there's
AppDomain for example and the list starts with
AccessViolationException and ends with {} Web
System.Text.ASCIIEncoding does work
but again
import System.Text
System. does not work
System.Text. does not w
Piotr wrote:
> Dino:
> thank for the explanation for the clr.Reference.
>
>
>
> >> > import System.Text as text
> >> > text. produces autocompletion list
> >> >
> >> > whereas
> >> >
> >> > import System.Text
> >> > System.Text. does not
> >
> > Does "Text." give you completions? We could ju
Dino:
thank for the explanation for the clr.Reference.
>> > import System.Text as text
>> > text. produces autocompletion list
>> >
>> > whereas
>> >
>> > import System.Text
>> > System.Text. does not
>
> Does "Text." give you completions? We could just be misanalysing the
> import statement.
Piotr wrote:
> > I have a feeling that getting autocompletion/intellisense for CLR
> > libraries referenced that way is not a trivial task, though it's
> > probably not impossible. What we ended up doing is writing a Python
> > 'pretend' module for our CLR assembly and importing that, but doing
>
Hi Daniel,
thanks for the response.
> I have a feeling that getting autocompletion/intellisense for CLR libraries
> referenced that way is not a trivial task, though it's probably not
> impossible. What we ended up
> doing is writing a Python 'pretend' module for our CLR assembly and importing
I have a feeling that getting autocompletion/intellisense for CLR libraries
referenced that way is not a trivial task, though it's probably not impossible.
What we ended up doing is writing a Python 'pretend' module for our CLR
assembly and importing that, but doing trickery so that the names ac
Hi,
I am using VS 2010 and IronPython 2.7B1 and noticed that
autocompletion works for "native" (Iron)Python modules (e.g. math).
However when I try to import a 'dll' module
# Program.py
import clr
clr.AddReference('ClassLibrary.dll')
from ClassLibrary import *
x = SomeClass()
x.Value = 1
x.
