tooltips for members of classes [RESOLVED]

[Andy]

arent the tooltips supposed to pop up in intellisense when you start typing stuff in? I compiled about 6 classes into one .dll and each property and each method and each class has a ///summary section but not one of them are being displayed.

What am i doing wrong?

I compiled and referenced the dll from the DEBUG folder of the c# project in my vb test project. Should I be compiling a 'release' build?

[JAtkinson]

Ive had this same problem in my classes. I would use the /// above the methods and also go to the project properties and set the XML to save like it should. Yet, when I built the solution and used the dll, I still didnt get any comments in intelliscense other than what type of variables are accepted.

[Memnoch1207]

I assume you compiled the dll with the proper switch to create the comment file?

[JAtkinson]

Could you give a few more specifics?

[Memnoch1207]

from the command line, VS.Net doesn't support this.

If you want to compile you class and export you comments to an xml file just do this

Assume file is Test.cs

csc /doc:Test.xml Test.cs

[Andy]

from the command line? I've always used the Build menu option. How do you use the command line? is it the same cl as Start/Run/cmd?

[Memnoch1207]

Yes, you have to use the command line to compile the comments in C#, because this is a feature that VB.NET doesn't have.

If you have VS.NET, then the command prompt should be located at.

Start>Programs>Microsoft Visual Studio .NET>Visual Studio.NET Tools>Visual Studio.NET Command Prompt

[hellswraith]

Originally posted by Memnoch1207
from the command line, VS.Net doesn't support this.

If you want to compile you class and export you comments to an xml file just do this

Assume file is Test.cs

csc /doc:Test.xml Test.cs

The IDE sure does support this functionalily. Right click the project, go to properties. Then click on the Configuration Settings section. You will see a XML Documentation File setting. Put in the filename there. Use the same name as the project itself but with a .xml extension.

[hellswraith]

Another thought if the above doesn't work. You need to comment ALL publicly accessible members in each class. For some reason the compiler will trip up on it sometimes if it encounters a public variable or method that doesn't have a comment. (even the constructor needs a comment sometimes). This doesn't happen all the time, but I have seen it get tripped up before.

Next, go ahead and compile your project, it will generate the document file. Now unreference and rereference your dll in your other application. They should then show.

Had the same problem a bit ago and that was how I solved it.

[Memnoch1207]

Excellent. I didn't know that was there!
Know I don't have to keep using the f***ing command line to do it!

Thanks Hellswraith!