Can intellisense be exported or extracted from Visual Studio to a text file?

Question!

I'm trying to write some documentation for a webservice that has been provided by one of our vendors for an application we're integrating. A bunch of the interface is custom objects defined in the web service itself. The vendor has put up significant resistance to providing any documentation for this application and so I've taken it upon myself to do their job for them [against my better judgement].

The documentation they have provided frankly is embarassing and I'm trying to make as short work of this as I possibly can to put some good quality docs together. I know that as I don't have access to their source, I can't just run it through nDoc/Sandcastle to spit out an API doc, but I was wondering if (as a half way house) there was an easy way to export the intellisense to a text file without me having to write a utility to specificially iterate through each of the object types defined and reflect the members out to text?

If I could do this, it would at least make sure that I have a good quality document structure where I can just fill in the blanks. Having to skip back and forth to Visual Studio to check the intellisense for every class member is a very laborious way of doing this.

Does anyone have any ideas?



Answers

I think VS.net generates documentation for intellisense. For existing assemblies, it is already on your file system (e.g. C:\Windows\Microsoft.NET\Framework\v2.0.50727\en)

Try using the assembly from the vendor in VS.NET. Use process explorer or any such tool from sysinternals to see what files are being loaded. I am sure, you will find that there is an xml file created for the custom assembly (which is used to show the Intellisense and documentation available with it).

Hope that helps.

EDIT: I think the same folder (where your custom assemblies are located) will have the xml files for documentation.



I know it's not your question, but how many singletons do you have such that you require an interface? This smells like bad design to me - can you explain clearly why these classes should be singletons rather than instances? If your answer is memory, I would suggest your overthinking your application, and if you're really concerned, look into the flyweight pattern (or perhaps a simple factory pattern). Sorry for not answering the question directly, but this doesn't sound like a great idea.

By : Travis


John Englehart (regexkitlite developer) has posted to cocoa-dev saying that apps are being rejected for using it. http://lists.apple.com/archives/Cocoa-dev/2010/Jun/msg00564.html

(Apologies for this purporting to be an "answer", it would be a reply to Kendall Helmstetter Gelner if only I had 49 more reputation points).

By : bonaldi


This video can help you solving your question :)
By: admin