What I think might help your particular problem is this:
1) Putting the
[DesignerSerializationVisibility(DesignerSerializationVisibility.Hidden)]
attribute on your property. This will stop the designer from serializing
your property to code in the typical way.
2) You need to create a designer cl
So could you have an .aspx file that has all the references in it (I assume
you are calling this from a handler), and then you can call
PageParser.GetCompiledPageInstance on the "include" page, which will cause
the right types to be associated with the right file names, and then when
you call GetCo
Because I'm not creating the page from another page.
Jim
- Original Message -
From: "Jon Flanders" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 28, 2003 4:45 PM
Subject: Re: [ADVANCED-DOTNET] Problem with ASP.Net's parser
> Sorry - can you explain why you have to c
Fritz Onion's "Essential ASP.NET" discusses control interaction with the
designers, editors, and other aspects custom control development and IDE
interaction. I believe he also has examples of IDE interaction with
ASP.NET controls on his web site (http://staff.develop.com/onion/).
Bob Beauchemin
h
Hi Howard,
I did find one book on Amazon which sounded like it may be suitable.
It's called 'Developing .NET Custom Controls and Designers Using C#'. The
author is James Henry.
Unfortunately, it doesn't seem to currently be stocked by any retail stores.
I'm hesitant to buy it without being able
Stefan,
Thank-you for your kind offer. After receiving your reply, I started over
and rewrote the code from scratch (intending to send you a copy). The new
code is working perfectly. I'm reviewing the old code and I'll post
another reply once I figure out what I did wrong. Thanks again,
- Eri
Sorry - can you explain why you have to call GetCompiledPageInstance and not
use @Reference?
> In any event, I don't believe GetCompiledPageInstance was intended to be
> called in this manner. Using the Reference directive is the standard way
of
> including another .aspx file.
This isn't an opti
Jon, inline...
> The reason that adding the Reference directives fixes the problem, is
> because internally inside of the call to GetCompiledPageInstance - the
> ASP.NET runtime is parsing each file seperately and compiling them (i.e.
not
> calling GetCompiledPageInstance again). GetCompiledPageI
Phil,
I am currently facing a similar dilemma. The closest reference that I've had to go on
is the mspress book on developing asp.net server controls. However, like the msdn
documentation, the book kind of leaves you to infer ide behavior outside the context
of server controls. One book tha
Yep, thanks Rodrigo.
MCA
> -Original Message-
> From: Moderated discussion of advanced .NET topics. [mailto:ADVANCED-
> [EMAIL PROTECTED] On Behalf Of Rodrigo B. de Oliveira
> Sent: Thursday, February 27, 2003 8:49 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [ADVANCED-DOTNET] Need Help wit
> why is the comparison to 0 done twice?
Because of the logical negation. Oddly, there's no logical-NOT instruction
in IL, so when the C# compiler needs to invert a Boolean on stack, it emits
ldc.i4.0
ceq
Not to worry, though - I'm sure it'll be optimized by the JIT'er.
- Per
- Ori
Erik,
I tried to reproduce your secoind test case, i.e. make late-bound calls
to a context-bound object through reflection, and I can't reproduce the
behaviour you described.
Using some AOP-like services I implemented myself a little while ago, I
defined a textbook 'tracable' class. I put this cl
Ug, sorry, never noticed the bottom half of your message. Yeah that is
weird, I would guess it just was an optimization that didn't mention itself
to the rest of the equation.
I'll look closer next time!
> Given this source code
>
> C# source:
> public bool IsIndexed {
> get { return (SearchF
Simon,
The (intended) comparison is actually just done once. The surprising fact
is that MSIL doesn't have a "cnq" (compare not equal) instruction, only a
"ceq" (compare equal) instruction.
So if you compare a test value for inequality to zero, the MSIL code must
first determine the test value's
Simon,
>why is the comparison to 0 done twice?
Well, you should think of the second 0 as the constant for false. So an
expression x != 0 gets deduced like this:
x != 0
!(x == 0)
(x == 0) == false
(x == 0) == 0
x == 0 == 0
You could also reason the other way around: what if t
The reason that adding the Reference directives fixes the problem, is
because internally inside of the call to GetCompiledPageInstance - the
ASP.NET runtime is parsing each file seperately and compiling them (i.e. not
calling GetCompiledPageInstance again). GetCompiledPageInstance is only
intended
...because the attribute can have more than one flag set. In C# you have to
explicitly compare non zero values to zero, because !=1 is not the same as
true..
Cheers,
Robin
> Given this source code
>
> C# source:
> public bool IsIndexed {
> get { return (SearchFlags & (int)
> AttributeSearchFl
He he,
Gavin Dock posted the solution on another list: use [XmlText()] attribute
and all works as required.
Thanks Gavin!
MCA
> -Original Message-
> From: Moderated discussion of advanced .NET topics. [mailto:ADVANCED-
> [EMAIL PROTECTED] On Behalf Of Mike Amundsen
> Sent: Thursday, Fe
Because the code uses !=, not ==; so the first comparison tests whether
(SearchFlags & (int) AttributeSearchFlags.Index) is equal to zero; and
the second tests whether the result of that comparison is false.
-Original Message-
From: Moderated discussion of advanced .NET topics.
[mailto:[EM
Use XmlText instead of XmlElement in the Category property.
Instead of:
[XmlElement("category")]
public string category {}
Use:
[XmlText]
public string category {}
Rodrigo
- Original Message -
From: "Mike Amundsen" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 2
20 matches
Mail list logo
