I know that ILDASM can show me this information but I need library for my
> project.
> Any ideas?
You could try Lutz Roeder's ILReader library [1]
[1] http://www.aisto.com/roeder/dotnet/download.asp?File=ilreader.zip
--
Tomas Restrepo
[EMAIL PROTECTED]
You can read messages from th
; you mean those with non-proportional spacing...).
--
Tomas Restrepo
[EMAIL PROTECTED]
You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
They _could_ have used a method forwarding strategy. In fact, that would've
been fairly easy to build a compiler that does it automatically. OTOH, I'm
personally not very keen on that kind of things... it can be confusing to
have the compiler inserting methods with commonly used names. (or
an the recommended instance method called Add?
Because that's the operator itself. IOW, Managed operators are nothing more
than static methods with a known name and marked with the specialname
metadata attribute in the signature.
--
Tomas Restrepo
[EMAIL PROTECTED]
You can read messages fr
the Platform SDK docs (although I don't remember exactly where_).
--
Tomas Restrepo
[EMAIL PROTECTED]
You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
use an alternative like NAnt) -- the
>longshot. :)
I'd argue that even with 3, Option 1 is what should be done, as long as you
correctly control the granularity of your assemblies (which shouldn't be
hard)./
--
Tomas Restrepo
[EMAIL PROTECTED]
You can read messages from the DO
for it, that's how it goes...
--
Tomas Restrepo
[EMAIL PROTECTED]
You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
Ovidiu,
> reinvent the wheel all over again. Who knows what *common feature* I'll
have
> to implement next time?
Oh, I totally agree. In fact, I remember complaining about this same issue
like a year ago ;)
--
Tomas Restrepo
[EMAIL PROTECTED]
You can read messages from the DOT
: Raise events
from the toolbar's buttons when they are clicked. I even went one step
further and allowed toolbar buttons to be hooked up to corresponding menu
items so that you would only need to write a single event handler, much like
you do in mfc...
--
Tomas Restrepo
[EMAIL PROTECTED]
You can
etOption, like this:
s.SetSocketOption (
SocketOptionLevel.Socket,
SocketOptionName.ReceiveTimeout,
TIMEOUT
);
(where TIMEOUT is the timeout in ms you want...)
--
Tomas Restrepo
[EMAIL PROTECTED]
You can rea
XML, an
element's attribute is itself a node, just as the text inside an element's
opening and closing tags are, and neither of them certainly have a />.
Processing instructions, like the other two, are just some kinds of nodes,
different from elements. (Heck, even comments in XML
Franklin,
> BTW, I knew that the first line was correct as in it is part of a
document, but it isn't a > node ...
It _is_ a node, just not an element node (it's actually a processing
instruction node, but that's another matter ;))
--
Tomas Restrepo
[EMAIL PROTECTED]
You c
Drew,
> I'm sure someone has to have already written one of
> these.
Well, in that case, I guess SysInternal's excellent DebugView [1] would be
more than enough.
[1] http://www.sysinternals.com/ntw2k/freeware/debugview.shtml
--
Tomas Restrepo
[EMAIL PROTECTED]
You can read m
Hi Chris,
> Anything else? Anyone done any of this work yet?
I'd add:
- All designer settings (XML/HTML/WinForms)
- Debugger Settings
- Customized TaskList Comment Tokens
--
Tomas Restrepo
[EMAIL PROTECTED]
You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
s
rs and libs (much less desirable, imho).
--
Tomas Restrepo
[EMAIL PROTECTED]
You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
Only if it's larger will an
external buffer be allocated on the heap and a pointer to it stored in _Ptr.
Regardless of that, you can be sure string::c_str() will return a pointer to
the actual storage of the string.
--
Tomas Restrepo
[EMAIL PROTECTED]
You can read messages from the DOTNET a
Miguel,
> Sorry if you misunderstood me, but i´m not converting a LPCSTR, i´m
converting a
> std::string, from .
Then just do
new String(myStdString.c_str());
--
Tomas Restrepo
[EMAIL PROTECTED]
You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscr
ther server)...
--
Tomas Restrepo
[EMAIL PROTECTED]
You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.
al with projects of
at least medium complexity, it's build system is pretty much useless except
for the smallest projects.
P.S. If you think you're having problems with 14 projects in a solution, try
working on one with 32
[1] And yes, it _does_ happen with separate build directories
uld likely be _not_ putting the managed class
into the static library too, just put them completely separate.
But now that I think about it, I can't see why the compiler wouldn't be able
to do the same on a .LIB, since they are, after all, PE files, too. Never
tried it, though...
--
To
class itself could be allocated where the managed runtime
has no control, such as in the unmanaged heap. So, extraq support, in the
form of GCHandle (or gcroot, which wraps it) is needed to tell the runtime
that you still hold a reference to the object.
--
Tomas Restrepo
[EMAIL PROTECTED]
You can r
21 matches
Mail list logo