For this first release we wanted to concentrate on writing and testing the class libraries (and there was dual language support happening of course *g*), so the installation is relatively rudimentary. However, you can install it in locations other than the suggested location.
>
>If you want the Toolkit to appear in the Add Reference, .NET tab list as the Readme suggests, then you will want to change the REG file.
>
>1. Edit the VFPToolkitNET.reg file in Notepad
>2. Change the registery key to point to your desired location, save and close the file
>3. Double-click on the REG file.
>
>That should do it. But, note that you don't have to register the assembly at all in order to use the Toolkit in a .NET project. When you add a reference to it, simply chose the browse option instead, and navigate to your location.
>
>If you install in a location other than the default the dynamic help will not work correctly, but for many of us who don't normally display dynamic help, that shouldn't be too big of a problem. Intellisense will still work and the help file will work as a normal CHM.
>
>HTH. If not, please let me know how it goes.


Hi Nancy,

Well then, I think for now I'll leave it where it is on c:\ for now... especially since I'm going to be needing a lot of help with this whole .NET thing. :)

BTW: Thanks to you and the rest of the team for the work you've all done on this.


- Brian