I've never been able to use any Sage control on DotNet projects.  Only VB6 works.

Do you have any other projects that have worked this way?  Mirroring what Jay said, I haven't been able to get screen mods to work in .Net (or Delphi, for that matter).

As an aside, many of us have switched over to using Orchid's Extender product for doing customizations.

Indeed, Extender is great!

In previous version SAGE 2018. I can successfully created a customize project using .NET. After I upgraded to latest SAGE version. Cannot anymore. This Orchid's Extender is free to use?

Oh, my, no, it's not free.  But speaking as a career Sage developer and integrator, it's worth every penny.  We install it at nearly all of our medium to large clients.  It's deep and wide.  And you get to try and remember the Python you learned at university!

I've just tried it on a dev machine with no issues. Running VS 2019 v16.7.6, with Sage 300 2020 PU2.

I created a new c# .NET win forms app. Changed the target type to x86. Created a new form. In the toolbox I added the AP2100 control and dragged it in. It automatically referenced accpacCOMAPI, the datasource, etc. All that can be seen from the screen shot below. No issues.

I have a few projects on Sage300 2019 using WPF with sage finder controls working all ok.

Can i suggest that you check the target type is x68 and clear your obj and bin folders - then clear your solution.

The only issues I've encountered is when upgrading projects to later versions of Sage300. I basically have to remove all references that are auto-created, clear the solution (and delete the the obj and bin folders), then add the updated controls to the toolbox and drag them into a dummy form. It automatically add all new references and updates the existing controls.

All my application are x86. Already tried to clear the obj and bin folder but still no luck, also creating new project still having the ActiveX error. Next I will try to upgrade to PU2. Thanks for the input.

maybe even try running VS under admin elevation?

Running my VS as admin still throwing same error.

do you have any clean machines that you can try it on? I tested it on an old 2016 VM that I have and it throws the same error. Having said that, i tried it on another 2016 VM and it works 100%. :/

Hey, We've recently resolved this issue or at least have an immediate solution as we address a long term solution. It seems that the ObjSafe.tlb file is being removed during the installation, likely by an anti-virus program. Since the VB UIs are built with the lObjectSafety implementation, when this file is missing, the axInterop utility complains.

Short Term Solution: Here is a link (www.dropbox.com/.../ObjSafe.zip) to a zip file containing the ObjSafe.tlb file. Unzip into your Sage Runtime folder and the issue is resolved and you can now add the OCX to the Visual Studio Toolbox and then drop it on your WinForms screen (C# or VB.Net).

Long Term Solution: We may decide to remove the lObjectSafety implementation in the VB UIs (single implement statement) since the VB OCXs are no longer supported being run in Internet Explorer.