MySQL Bugs: #8361: Connector dll not placed in correct folder for add reference dialog

Bug #8361	Connector dll not placed in correct folder for add reference dialog
Submitted:	8 Feb 2005 0:33	Modified:	28 Feb 2005 0:10
Reporter:	Simon Rigby	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / NET	Severity:	S3 (Non-critical)
Version:	1.0.4 (GA)	OS:	Windows (Windows XP Pro)
Assigned to:	Reggie Burnett	CPU Architecture:	Any

Description:
When running the installer for the component it does not place a copy in the folder Visual Studio uses for the .NET tab of the add reference dialog box.

How to repeat:
Run the installer. Add a reference to a project in VS.NET. The component does not appear in .NET tab.

Suggested fix:
Either have the assembly copied to the appropriate directory (in the case of Visual Studio 2003 - C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE\PublicAssemblies). In addition, I believe a registry key could be added to allow VS.NET to find the item at the default install location (key unkown).

The Installation Directory is ok and a Registry key is also created, but it points to the wrog directory.
The key created by the installer is:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\7.1\AssemblyFolders\MySQL Connector Net 1.0.2]
@="C:\\Programme\\MySQL\\MySQL Connector Net 1.0.4\\\\bin\\NET 1.1\\"

But should be:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\7.1\AssemblyFolders\MySQL Connector Net 1.0.2]
@="C:\\Programme\\MySQL\\MySQL Connector Net 1.0.4\\bin\\.NET 1.1\\"

After changing this key you can find the component in the "Add Reference" Dialog of VS.Net

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Thanks for the report.  This has been fixed.