On 8/17/2011 8:10, Invisible wrote:
> Now that's irony. :-D

It's basically a different "project explorer". Just like you have in Word or 
Excel.

> Anyway, I'm not sure you can use this to customise the behaviour of the IDE.
> Looks like it's only useful for automating tasks that the IDE itself can
> already perform...

http://msdn.microsoft.com/en-US/library/345xe6tb%28v=VS.80%29.aspx

http://msdn.microsoft.com/en-US/library/0b27f9kz%28v=VS.80%29.aspx

And how do you automate something in elisp that emacs can't already do? What 
kind of thing do you think elisp can do that a macro with complete access to 
both native code and the full DOM of the entire development environment 
can't do?

Pretty sure emacs cannot, for example, do this:
http://msdn.microsoft.com/en-US/library/envdte80.events2.debuggerprocessevents%28v=VS.80%29.aspx


Unfortunately, it's extremely annoying that text in MSDN web pages doesn't 
HTML-link to the descriptions of the classes that various methods take and 
return. So if you have a method that returns a ProcessItem or something, you 
actually have to go search for "ProcessItem class" instead of just clicking 
the name to get to the docs. Like MS never really figured out that whole 
HTML anchor/link kind of thing.

-- 
Darren New, San Diego CA, USA (PST)
   How come I never get only one kudo?

Post a reply to this message