Author Topic: Compatibility with older VB Controls  (Read 2385 times)

arbor

  • Newbie
  • *
  • Posts: 9
    • View Profile
Compatibility with older VB Controls
« on: June 05, 2015, 09:04:33 AM »
I am wanting to use your HMI with AB compactlogix and Keyence camera controller. I installed Visual Studio 2013 Community. When trying to add COM Component, VWXG Control (Keyence camera control Active X), get message "added...but not enabled". Keyence documentation says compatible with VB2010. Any workarounds or do you have earlier AdvancedHMI software that will run on VB2010? Thanks much. 
« Last Edit: June 05, 2015, 09:06:14 AM by arbor »

arbor

  • Newbie
  • *
  • Posts: 9
    • View Profile
Re: Compatibility with older VB Controls
« Reply #1 on: June 05, 2015, 09:30:15 AM »
Just received reply from Keyence, "According to our most updated manual, the Active X package is compatible with
VB 6.0, VB 2005, VB 2008, and VB 2010.  I would assume VB 2013 would be fine,but have no way to confirm as we are working with VB 2008."

Archie

  • Administrator
  • Hero Member
  • *****
  • Posts: 5269
    • View Profile
    • AdvancedHMI
Re: Compatibility with older VB Controls
« Reply #2 on: June 05, 2015, 09:40:19 AM »
Typically compatibility problems are more with the .NET framework version than the Visual Studio Version. AdvancedHMI is based on .NET 4.0

The latest release of AdvancedHMI still works in Visual Studio version as far back as 2010 as long as Service Pack 1 for Visual Studio 2010 is installed. You can try this with Visual Basic Express 2010 and the service pack.
« Last Edit: June 08, 2015, 07:19:02 AM by Archie »

arbor

  • Newbie
  • *
  • Posts: 9
    • View Profile
Re: Compatibility with older VB Controls
« Reply #3 on: June 08, 2015, 05:34:52 AM »
Thanks Archie:
I am getting errors when I try to build AdvancedHMI in VB Express 10 that it cannot find Controls or Drivers. Tried to build them first, no luck yet. Also added file loacations in references in each. Is there a specific file location for the AdvancedHMI project? I realize this is probably all due to my lack of VB experience, but sure would appreciate a little guidance.

Archie

  • Administrator
  • Hero Member
  • *****
  • Posts: 5269
    • View Profile
    • AdvancedHMI
Re: Compatibility with older VB Controls
« Reply #4 on: June 08, 2015, 07:20:02 AM »
Can you post the exact error message you are getting?

arbor

  • Newbie
  • *
  • Posts: 9
    • View Profile
Re: Compatibility with older VB Controls
« Reply #5 on: June 08, 2015, 07:51:25 AM »
this is before building

arbor

  • Newbie
  • *
  • Posts: 9
    • View Profile
Re: Compatibility with older VB Controls
« Reply #6 on: June 08, 2015, 07:52:38 AM »
and after build

Archie

  • Administrator
  • Hero Member
  • *****
  • Posts: 5269
    • View Profile
    • AdvancedHMI
Re: Compatibility with older VB Controls
« Reply #7 on: June 08, 2015, 08:12:06 AM »
That almost sounds like the AdvancedHMIDrivers and AdvancedHMIControls projects are not part of the Solution. What do you see in the Solution Explorer?

Also try this:

- Exit Visual Studio
- Go to AdvancedHMIControls folder and delete \bin and \obj directories
- Do the same with AdvancedHMIDrivers folder and the AdvancedHMI folder
- Open the Solution again and Rebuild All

arbor

  • Newbie
  • *
  • Posts: 9
    • View Profile
Re: Compatibility with older VB Controls
« Reply #8 on: June 08, 2015, 08:52:27 AM »
I noticed that I can open the VBPROJ file in AdvancedHMI but not the SLN file since it says "created with newer version" and I am using VB Express 2010. Does this matter? Is so, do you know workaround? I have verified the keyence activex control works in 2010 but not 2013.

Archie

  • Administrator
  • Hero Member
  • *****
  • Posts: 5269
    • View Profile
    • AdvancedHMI
Re: Compatibility with older VB Controls
« Reply #9 on: June 08, 2015, 09:09:32 AM »
That error generally means the service pack is not installed. Go to Help->About to check. If it does not show the service pack, go to Microsoft downloads and search for Visual Studio 2010 service pack.

arbor

  • Newbie
  • *
  • Posts: 9
    • View Profile
Re: Compatibility with older VB Controls
« Reply #10 on: June 08, 2015, 09:12:56 AM »
Thanks Archie for the guidance. Seems to be building without errors now. I will probably be asking more questions once I actually start using! Bill

arbor

  • Newbie
  • *
  • Posts: 9
    • View Profile
Re: Compatibility with older VB Controls
« Reply #11 on: June 12, 2015, 10:32:16 AM »
Archie:
Wanted to let you know everything is working. When adding a duplicate visual control on a screen, do I need to change it's name? Thanks again. 

Archie

  • Administrator
  • Hero Member
  • *****
  • Posts: 5269
    • View Profile
    • AdvancedHMI
Re: Compatibility with older VB Controls
« Reply #12 on: June 12, 2015, 10:58:25 AM »
When adding a duplicate visual control on a screen, do I need to change it's name?
If you add controls to the form in the designer, it will assign a default name that is unique. You can leave this name, but it is usually helpful if you change it to something meaningful.