Ocx which developed by FMC add to Asp.Net

Question

Ocx which developed by FMC add to Asp.Net

GuoJunjie 20

I have developed an OCX by MFC AcxtiveX in Vs2019. This OCX can be added to Toolbox in Winform. But can be added to ASP.NET toolbox. When I tried to add it to toolbox. A Error massage occurs “The controls is successfully added to toolbox ,but it can be enabled in current design”. How to solve the problem?

Albert Kallal 3,451 Reputation points

2023-02-28T03:13:30.61+00:00

Modern browsers will not support ActiveX controls - they were depreciated QUITE a long time ago, and as such, use of such controls will simply not work in a modern browser setup. You might be able to get this by VAST changing browser security settings, but it really not practical for use in a web browser. If you want to create some kind of re-usable control, then in asp.net create a Web forms user control, and you can then create that control using standard markup. And with more experience, then you can even consider creating a Web forms server control, but they are quite a bit more work.

All in All? You not get a ocx control to work in web forms with any real luck, since browsers long ago dropped support for ActiveX controls.
GuoJunjie 20 Reputation points

2023-03-02T01:31:47.18+00:00

Dear Albert Kallal :

Thank you very much. I’m newer for Web App developer. We have developed a package Wpf Application for industry real time control with some third wpf’s dll. Now we want to transfer part of control information to Web . The Wpf App is still be used and extend for new requirements . We wangt to refresh the Web App at same time . Is there any way to do that within Vs2019?

Thank you very much for your help again.
Albert Kallal 3,451 Reputation points

2023-03-02T02:00:35.2466667+00:00

Well, you can certainly build some page on a web site, but that page of it own accord can't say communicate with say some hard ware device. If you have some kind of system that can push out data to say a database, then a web site can display such information. However, as I stated, those desktop controls and interface simply can't be used in a web browser. You can no more do this then you can turn a bicycle into a helicopter. (why: because a bicycle and a helicopter are not the same thing - that's why!!!). So, you don't say "what kind" of control you want to transfer to the web. That web based browser say running on my computer has ZERO ability to mess around with my hardware (let alone use windows desktop controls). So, if some type of hard is to be attached to say some computer that logs data to a database, then a web display can thus consume that data. However, the web browser is locked down from touching hardware on the computer the browser is running. (not like YOUR web site going to say look around at my hardware, or grab my banking or accounting files on my computer). So, a web browser is 100% sand boxed from touching the computer hardware, and if web browsers were not locked down this way, then no one would EVER risk using a web browser, since when you come to my site to look at a cute cat picture, the web site could then start messing around with YOUR computer and grab files and do all kinds of things.

So, we dealing with two issues here:

Software written for the windows desktop can no more run on a Apple Mac, or say a Android phone - they are vast different architectures here. So, those desktop components can't be used for or in a web browser.

And then the next issue is what kind of information are you to display in that web browser? You can quite much display any information and have some "very" cool looking dashboard in a browser. However, that information for that display has to come from the web server. So that web browser can't touch, or communicate with ANY of the hardware from the "client" computer that hosts that browser, since as I noted this would be far too great of security risk. (the web browser has ZERO knowledge of your hard drive, files, and any devices attached to that computer.

Now, if some hard ware data device "sends" data to some server? And that server shares its data with the web server? Ok, now ANY web browser can thus receive data from that web server, and thus display some cool dashboard and system.

However, the client side web browser + system can't touch or communicate with ANY hard ware on that computer that runs the browser - (its in that sand box).

So, a web based UI can quite much be anything you dream up, and can certainly be as rich and cool as a desktop program. But, that would only be the "UI" part, since the web browser as noted can't touch or communicate with hard ware attached to that same work station.

So, web based software can't use "windows" controls anymore then software written for FoxPro or vb can be used on a android phone, or some Atari computer. And web based software has the additional limitation that it can't touch nor communicate with any hardware on which that computer that is running that browser instance.

Albert Kallal 3,451 Reputation points

2023-02-28T03:13:30.61+00:00

Modern browsers will not support ActiveX controls - they were depreciated QUITE a long time ago, and as such, use of such controls will simply not work in a modern browser setup. You might be able to get this by VAST changing browser security settings, but it really not practical for use in a web browser. If you want to create some kind of re-usable control, then in asp.net create a Web forms user control, and you can then create that control using standard markup. And with more experience, then you can even consider creating a Web forms server control, but they are quite a bit more work.

All in All? You not get a ocx control to work in web forms with any real luck, since browsers long ago dropped support for ActiveX controls.
GuoJunjie 20 Reputation points

2023-03-02T01:31:47.18+00:00

Dear Albert Kallal :

Thank you very much. I’m newer for Web App developer. We have developed a package Wpf Application for industry real time control with some third wpf’s dll. Now we want to transfer part of control information to Web . The Wpf App is still be used and extend for new requirements . We wangt to refresh the Web App at same time . Is there any way to do that within Vs2019?

Thank you very much for your help again.

Answer 1

Hello @GuoJunjie ,

Welcome to Microsoft Q&A forum.

The error message did mention => The control is successfully added … but it can’t be enabled in current design. So you may consider why it can’t be enabled. Probably you didn’t open the designer view for one of the web page that you are developing on.

Please try to select and right-click the file(for example, xx.aspx) => click "View Designer" => and then try to add your control to the toolbox(right-click any white space in Toolbox window => click "Choose Items…" => switch to "COM Components" tab => check your control => confirm if it is added successfully and listed in Toolbox window).

Please feel free to contact us, have a nice day.

Best Regards,

Tianyu

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Dear Albert Kallal :

Thank you very much. I’m newer for Web App developer. We have developed a package Wpf Application for industry real time control with some third wpf’s dll. Now we want to transfer part of control information to Web . The Wpf App is still be used and extend for new requirements . We wangt to refresh the Web App at same time . Is there any way to do that within Vs2019?

Thank you very much for your help again.

Answer 3

GuoJunjie 20

User's image

I was to it with way you recommended as follows

User's image

But in the toolbox. It still shows a gray icon and can’t be added to designer

If I switch to the Winform designer the Ocx is OK.

How to solve the problem

Albert Kallal 3,451 Reputation points

2023-03-02T03:05:05.63+00:00

You perhaps did not grasp what I stated. but, in VERY simple terms? You simply can't use those desktop controls for web based development, it is NOT possible and will not work. And those .dll's you have? If they are pure code without ANY UI components, then you can use those .dll's on the web server side only, but not on each users desktop with the browser.

If those .dll's contain ANY windows user interface code or dialogs, then again they can not be used. So, no, this is not possible, not allowed, and will NEVER work, and it can't work. You have to adopt web based controls ONLY and ONLY components for web development.

Any controls and code for windows desktop controls or interfaces have to be 100% re-written, and you can't re-use those controls.

So, there is not a answer here, and this is not some question of helping, it is a question of doing the impossible.

Web based development <> desktop development. Web based development has VERY little to do with desktop, and that includes attempting to use controls for the desktop in web based system. This will not work, and is not allowed.

This is "why" those controls are greyed out and disabled when you attempt to build web based software. So, no, use of those controls is not allowed, and will not work. You can ONLY use web based controls for web based software development - you have no choice in this matter.

If you want to un-gray and un-disable those controls, you have to create a desktop project and not a web one. The "act" of forcing those controls into the tool box means nothing here, and they are not in the tool box by default for a good reason (that reason is those controls don't work with web based software).

Ocx which developed by FMC add to Asp.Net

2 additional answers

Activity