Visual Studio AddIn - never put dots in a command.

I was following an article on how to create a command and add it to the Code Window context menu, it was going really well until some point.

I ran the code and Visual Studio was crying with E_INVALID_ARGS error on the

this._applicationObject.DTE.Commands.AddNamedCommand

This one is widelly used and pretty standard method so I thought the problem is somewhere in my code.

I realized that almost all the parameters I am passing to this method are pretty common as well so the problem must be at ....

Well, the command name I used was containing dots, that's why the error.
If you receive this message, please check the command name for dots (the second parameter you are passing to this method).

Since Visual Studio and other addin types seem to be working with very similar framework (the so called "extensibillity framework"), I suspect this rule is also applicable for other types of addins such as Outlook, Excel, Word, etc.

What happened with the Data mining?

Well, I simply stopped the project for a while, since I need to see the legal aspects of it. I am not quite sure if it is legal to simply take some catalogs from somewhere, reformat them and use them as your own. I think I can do such thing with some free public catalogs, but I will not act, until I have the written permission from the authors. Here are two screenshots of the spider in action : The above screenshot is when the spider is gathering data. It displays how much data is gathered and what the spider is doing in the given moment. The above screenshot displays the results of the crawl as a treeview. It uses MS Access database to store the data (since it is a small project). Technologies used for the spider :

/>.NET 1.1 (Windows Forms), MS Access, Internet Explorer Automation COM Libraries (AxWebBrowser, ShDocVW COM mshtml).