Invalid pointer exception after TeeChart upgrade

TeeChart for Microsoft Visual Studio .NET, Xamarin Studio (Android, iOS & Forms) & Monodevelop.
Post Reply
UserLS
Advanced
Posts: 247
Joined: Wed May 23, 2007 12:00 am

Invalid pointer exception after TeeChart upgrade

Post by UserLS » Mon Jan 12, 2009 3:44 pm

We upgraded TeeChart from an earlier version to version 3.5.3274.30664. Now, when we compile from Visual Studio 2008, the projects containing TeeChart references fail as follows:

'Could not load file or assembly 'TeeChart' or one of its dependencies. Invalid pointer (Exception from HRESULT: 0x80004003 (E_POINTER))'

What do we do to resolve this? Nothing has been changed except TeeChart was upgraded.

Narcís
Site Admin
Site Admin
Posts: 14730
Joined: Mon Jun 09, 2003 4:00 am
Location: Banyoles, Catalonia
Contact:

Post by Narcís » Mon Jan 12, 2009 3:47 pm

Hi UserLS,

You could try removing your project's TeeChart reference and adding it again.

If this doesn't help please send us a simple example project we can run "as-is" to reproduce the problem here. You can either post your files at news://www.steema.net/steema.public.attachments newsgroup or at our upload page.

Thanks in advance.
Best Regards,
Narcís Calvet / Development & Support
Steema Software
Avinguda Montilivi 33, 17003 Girona, Catalonia
Tel: 34 972 218 797
http://www.steema.com
Image Image Image Image Image Image
Instructions - How to post in this forum

UserLS
Advanced
Posts: 247
Joined: Wed May 23, 2007 12:00 am

Post by UserLS » Wed Jan 14, 2009 10:38 pm

Hi, I was able to get this resolved, but it was necessary to first uninstall your product. Then, I had to go through the registry deleting a large number of items that you added in the install for previous versions. Once I had done this and reinstalled the product, there were no problems.

It appears that your setup program fails to clean the registry of these old entries. This is particularly a problem regarding Visual Studio. I was able to build from a command-line MSBUILD, but could not build via Visual Studio. My guess is that the cause was the many Visual Studio registry keys you had pointing to your previous version.

Narcís
Site Admin
Site Admin
Posts: 14730
Joined: Mon Jun 09, 2003 4:00 am
Location: Banyoles, Catalonia
Contact:

Post by Narcís » Thu Jan 15, 2009 10:57 am

Hi UserLS,

Thanks for the information!
Best Regards,
Narcís Calvet / Development & Support
Steema Software
Avinguda Montilivi 33, 17003 Girona, Catalonia
Tel: 34 972 218 797
http://www.steema.com
Image Image Image Image Image Image
Instructions - How to post in this forum

UserLS
Advanced
Posts: 247
Joined: Wed May 23, 2007 12:00 am

Post by UserLS » Thu Jan 15, 2009 11:36 pm

No problem, but it would be nice if Steema could get this fixed.

Post Reply