I have a dotnetbar version 10.0.0.3 and when I add it on control toolbox window and drag it to my form this always happen.
as you can see, LabelX1, TextBoxX1 and ButtonX1 are in the form, but in the design it doesn't.
I had the same problem.
I think it's something about the dll.
I installed DevComponents.DotNetBar2 on my PC (it's a setup called DotNetBarSetup) and then
I got the dll-file from the HD
C:\Program Files (x86)\DotNetBar for Windows Forms\DevComponents.DotNetBar2.dll
Next, you have to drag the dll-file from windows explorer to the toolbox in Visual studio.
That should do the trick.
Hope this helps.
I had this problem in log time. finally i found the exact solution for this problem. The solution is install .NET Framework 3.5 (includes .NET 2.0 and 3.0) before install DotNetBar for windows form.
Hope this helps all the developers facing this problem.
Related
The problem is simple, this thing is just not installed.
And can't find any installer on the web.
"where wcftestclient" returns a not found.
When i press F5 and WCF project is selected, it just open my browser and show my svc. Useless.
What's wrong with my VS installation? Should i instal some SDK or so..?
Wanted to reinstal. Checked Windows Communication Foundation in visual studio installer components. Solved... sorry for not smart problem
My solution worked fine under Win8.1 using VS2013. Then I did a clean install of Win10. I ran the msi that was created back on XP some time ago, and it installed my VB app after asking for a .NET3 version. But then I started up VS2015 for the first time and loaded my VB app's solution. I get errors like this: BC30002 Type 'Excel.Workbook' is not defined.
I looked in Control Panel's Programs and Features and only see .NET 4.5 and 4.6 items (nothing for .NET 3).
My solution includes references to Microsoft.Office.Core and Microsoft.Office.Interop.Excel.
What do I need to do to fix this?
I solved this by going back to Control Panel/Programs and Features, selecting Microsoft Visual Studio Community 2015, clicking Uninstall or change a program. Then when the VS2015 installer opened, I selected Modify, then All (every installation option) and installed VS again. That solved the above problem.
But now I have a new error: BC30002 Type 'ExcelLateBind is not defined. How do I fix this?
I've created a C++ UWP Windows 10 app using Visual Studio 2015. However, I'm not able to visualize any xaml in the designer because I'm always getting a System.NullReferenceException error. How can I fix this?
That's very odd but I solved following these steps:
Close any instance of Visual Studio
Open Visual studio and create a new C# UWP empty project (name it as you like, do not matter)
Run the "useless" created project then close it as Visual Studio
Open again your previous C++ UWP project
In my case everything started working!
Switching solution platform to x86 worked for me.
I'm experiencing exactly the same problem on my primary development machine but not on another. The reason is... I think... When I installed Visual Studio 2015 on the 2nd machine, the first time I created a Universal Solution (C#) I was shown a dialog asking me to OK "elevated permissions" (custom permissions) for the VS2015 installation folder. I OK'd it and Designer works on that machine in both Blend2015 and VS2015 (community edition)
On the other machine I was never shown the dialog asking me to confirm elevated permissions and Designer does NOT work on that machine (VS2015 Enterprise). This machine also has VS2013 update 5) on it.
I am thinking that I might have to completely wipe off VS2015 and try to clean the registry of all VS2105 references AND remove the VS2015 installation directories on C:\ AND when I reinstall, create a installation directory with a different name (if I can). What a PAIN though... I'm waiting to see if MS delivers a simple solution since I'm quite positive that this whole issue boils down to a bug (feature... grrr) having to do with custom permissions that can't be changed (or added) after installation.
Would be nice is MS would confirm this...
(please note, none of this involved c++... it was all C#)
Tom
this is the dialog I was shown on the machine where Designer works]1
Installing the Windows Software Development Kit (SDK) for Windows 10 solved the issue for me. It may ask to unistall the previous version of Windows 10 RTM SDK
https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk
This is fixed in Update 1 of Visual Studio 2015
https://www.microsoft.com/en-us/download/details.aspx?id=49989
I am trying to upgrade a VB6 project to run it on VB8, but I am getting an error which says that you need to install TABCTL32.OCX(1.1.0).
What shall I do? Please Help.
Thanks in advance.
To run the upgrade wizard you need VB6 installed on the machine, and also any controls used in the code you are upgrading.
Tabctl32.ocx is the Tabbed Dialog Control 6.0, the standard tab control from VB6. If you install VB6 you will be fine.
See Microsoft's list of controls shipped with Visual Basic 6.
I'm experimenting with writing ActiveX controls and noticed that I can't seem to create an ActiveX control in Visual Basic (6.0) which features slightly more sophisticated controls. Simple controls like labels, buttons and check boxes seem to work fine, but as soon as I try to add e.g. a tree control to my form, the ActiveX control stays entirely blank as soon as I embed it into some host application on another computer. It works fine on my development box though.
While going through the Projects->Components (Ctrl+T) list, I found two libraries which apparently contain a tree control:
Microsoft Windows Common Controls 5.0 (SP2)
Microsoft Windows Common Controls 6.0 (SP6)
As soon as I add any of the controls from these libraries to my form, the form stays entirely gray when embedded on another computer. The other computer is a Windows XP system, so I hoped that missing redistributables wouldn't be an issue, given how old Visual Basic 6 is. To be sure, I installed the VB6 redistributables, but unfortunately that didn't make a difference.
Does anybody know why my ActiveX control would stay gray on other computers, but not on mine, as soon as I add any of the controls from the above libraries to me form? FWIW I just need a tree control so if there is some other, more appropriate, library available - that's fine with me.
UPDATE:
As it turned out, it helps to download MSCOMCTL.OCX into C:\WINDOWS\SYSTEM32 on the other computer and then registering it via regsvr32 C:\WINDOWS\SYSTEM32\MSCOMCTL.OCX. However, I didn't find an official source for this file, and running the COM registration by hand looks cumbersome to me. Is there really no redistributable I could use?
VB6 runtime is preinstalled on XP and above but the Common Controls component you are referencing is not.
Try installing Microsoft Visual Basic 6.0 Common Controls redistributable on the client machines or event better make a setup for your application.
Edit:
Opps, the link is for an update that does not install the OCXs if not already present. The only redistributable I find is a merge module for Windows Installer.
To solve this problem, I developed a .msi package. The source files (WiX) and stake posted here:
https://github.com/IT-Service/ITG.VB6CommonControlsRedist