I have a custom project in VB6, which I was working with it since 3-4 years ago, now today suddenly I noticed that Webbrowser controls are not working anymore on my laptop (maybe after a windows automatic update - it's working on my other laptop)
The problem is when I double-click on Webbrowser components there are no default declarations for them and this text shows up in code section:
Private Sub WebBrowser1_SHDocVwCtl(ByVal Text As String)
End Sub
Please help me fix it and get it back to how it was before.
As #JimmySmith suggests, check that Microsoft Internet Controls is checked in your Components list (Project > Components > Controls tab > Microsoft Internet Controls.). If not, check it and hit Apply, then OK.
If it doesn't show up in the list, you can use the Browse button to look for C:\Windows\SysWOW64\ieframe.dll directly.
Other things that I recommend:
Run VB6 IDE as Administrator. Right-click on your Microsoft Visual Basic 6.0 shortcut and check "Run this program as an administrator" in compatibility properties section.
Select Windows XP (Service pack 3) as Compatibility mode.
Related
Trying to follow multiple tutorials on adding RDP client support to an MFC project and I can add the ActiveX control just fine, but when I close the dialog in the resource editor then try to open it back up, I always get:
Microsoft Visual Studio
The ActiveX control "Microsoft RDP Client Control - version 11" could not be instantiated.
I then have to manually edit the .rc file and remove the control it added from the dialog. How do I stop it from doing this?
Two different tutorials can be found here and here
I recently came back to an Outlook add-in project, and I updated all of my Office apps. Outlook is currently Version 1906 (Build 11727.20244 Click-to-Run) on Windows 10 Pro (not running any insider’s version). However, after I open the add-in, no context menu opens when I right-click. I’m trying to debug the add-in running in native Outlook on Windows because something is broken (the same code works fine in OWA and Outlook for Mac).
I’m a bit stuck if I can’t attach a debugger. Nothing shows up in F12 developer tools either. However if I open the Insights add-in, I can right click and attach a debugger as you would expect.
Why would I not be able to even see the right-click context menu in my add-in?
However, after I open the add-in, no context menu opens when I right-click.
Try to create a new empty add-in in Visual Studio. If you get the context menu shown there, you just need to compare both projects and find the difference between them.
In my Visual studio 2012 for windows phone , I created one project and I developed some pages.
It is working fine and i'm able to debug by selecting the desired emulator option.
Suddenly the device options tab is not visible. It is looking like below.
For testing purpose I've opened another project, then for this project i'm getting the emulator option. It is looking like this.
I didn't understand why it is happening with the first project. could you please tell me how to enable emulator options for the first project.
Thanks.
If you have multiple projects in your solution then the one that is set as the 'StartUp project' is probably not a Windows Phone app.
The options included in the menu relate to the startup project only.
To change the startup project, right click on the project in the solution explorer and select "Set as StartUp project".
I'm running Microsoft Visual Studio 2010 Express for Windows Phone. My problem is I'm not getting the solution configurations drop down list.I tried a lot but I'm not getting it.
Click the Tools menu, click Settings, and then click Expert Settings.
The Solution Configuration list box appears in the Standard toolbar. Click Debug or Release.
If still not visible, check this
I've installed visual studio 2005 and windows embedded c.e. 6.0.
How do I create a simple hello world program in visual studio and then port it to a Win C.E. emulator and run the same there.
Does this page help?
Quoted from there:
Your First Visual C++ for Windows CE
Application
Your first Visual C++ for Windows CE
application will be a simple
application, a WCE MFC AppWizard (EXE)
to be precise. This application will
have a single view that will have a
bitmap painted on it. We will also add
a menu item that when clicked will
evoke a dialog. This dialog will
contain one of the Windows Common
Controls, a progress control. Creating
the Basic Application
Download the sample application source
code.
To start your first Windows CE
application we will generate a shell
using the WCE MFC AppWizard. The
numbered list below will step you
trough this process:
1. Open Visual C++ and go to the File menu and choose the New item
2. Select the Projects property tab if it is not already selected.
3. Select WCE MFC AppWizard (exe) in the list control.
4. Type WCEFirstApp in the Project name edit box
When you finish, you will see the New
dialog box as seen in Figure 3.
Press the Next button.
WCE MFC AppWizard (exe) - Step 1 of 4
will appear as seen in Figure 4.
Notice that the selections are similar
to the MFC AppWizard except that there
is no Multiple documents selection.
6. Accept the defaults.
7. Press the Next button.
WCE MFC AppWizard (exe) - Step 2 of 4
will appear as seen in Figure 5. There
are several options on this page. You
can add support for Windows Sockets,
ActiveX Controls, Windows Help, and
Printing if your target supports
Windows CE 2.1. You also can choose
the type of command bar that you wish
to support. For this exercise we will
accept the defaults.
8. Accept the defaults.
9. Press the Next button.
WCE MFC AppWizard (exe) - Step 3 of 4
will appear as seen in Figure 6. You
can choose to include generated
comments, an option that I highly
recommend. There is no such thing as
too much documentation. There is also
an option to link dynamically or
statically with the MFC Library.
Accept the defaults.
10. Accept the defaults.
11. Press the Next button.
WCE MFC AppWizard (exe) - Step 4 of 4
will appear as seen in Figure 7. This
page gives you an opportunity to set
the base class for the view. It also
gives you an opportunity to set your
file names. Accept the defaults.
12. Accept the defaults.
13. Press the Finish button.
The New Project Information dialog
will appear as seen in Figure 8. Just
like all Visual Studio AppWizards the
wizards give you a final chance to
look over your choices.
14. Press the Ok Button.
15. Select Build menu and choose the Rebuild All item.
When the application is completed
building, you are ready to go on to
the next section.
Also see this.