search

Prashant-Jonny / accord

Automatically exported from code.google.com/p/accord
0 stars 0 forks source link

Accord.dll doesnt properly register #21

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.Install Accord & AForge
2.Create project and add reference to the Accord.dll
3. The interfaces aren't recognized the the version information is 0.0.0

What is the expected output? What do you see instead?
It should show the versioning information in the reference. Instead I get a 
message the the file cannot be referenced

What version of the product are you using? On what operating system?
Win 7

Please provide any additional information below.

Original issue reported on code.google.com by GuyLeath...@gmail.com on 21 Nov 2012 at 10:01

GoogleCodeExporter commented 8 years ago 
The actual error is <The system cannot find the reference specified>
I copied the Accord*.dll files into the same directory as the project/solution 
and still had the problem.  I cannot use any of the library functions.  See 
screen shot.

Original comment by GuyLeath...@gmail.com on 26 Nov 2012 at 6:56

Attachments:

GoogleCodeExporter commented 8 years ago 
This seems weird. However, neither AForge or Accord register themselves in the 
GAC upon installation. Perhaps you could try removing all Accord/AForge 
references, then adding them by selecting "Browse" in the Add Reference Dialog 
and add the .dlls from there. Which version of Visual Studio (or other IDE) are 
you using?

Original comment by cesarso...@gmail.com on 26 Nov 2012 at 7:02

GoogleCodeExporter commented 8 years ago 
I have VS 2008 Developer Edition on Windows 7.  I tried adding the references 
by browsing to the DLL's.  Same problem. My colleague installed it on VS 2010 
and he didnt have this problem.

Original comment by GuyLeath...@gmail.com on 26 Nov 2012 at 7:37

GoogleCodeExporter commented 8 years ago 
Sorry, I didn't see your last comment until now. VS 2008 requires the .NET 3.5 
version of the framework. It is available as a separate download in the 
download page.

I will mark the bug as accepted because I will probably need to incorporate the 
3.5 assemblies into the main installer in order to avoid confusion, or make 
this warning more prominently.

Original comment by cesarso...@gmail.com on 15 Jan 2013 at 2:47

GoogleCodeExporter commented 8 years ago 
I had .NET Framework 3.5 installed and it still didn't work. 

Since the time I posted the problem, I upgraded to VS 2010 and it is working 
under this environment for me now.  It was just frustrating at the time because 
it was clear that Accord works under VS 2008.

Original comment by GuyLeath...@gmail.com on 15 Jan 2013 at 11:22

GoogleCodeExporter commented 8 years ago 
Sorry for the confusion. I actually meant the .NET 3.5 version of the 
Accord.NET Framework, not the 3.5 version of the .NET Framework itself. Since 
Accord.NET uses some specific features of .NET 4, there was a separate download 
for .NET 3.5, built around a compatibility layer for the missing features.

If you check the download page, there is a separate release for .NET 3.5 and VS 
2008. Those versions are available with a "net35" label, such as, for example

  https://code.google.com/p/accord/downloads/detail?name=Accord.NET%20Framework-2.8.1-%28v3.5%20only%29.rar

Sorry for not mentioning this earlier.

Original comment by cesarso...@gmail.com on 15 Jan 2013 at 11:34

GoogleCodeExporter commented 8 years ago 
Fixed on 2.9.0.

Original comment by cesarso...@gmail.com on 20 Apr 2013 at 5:25