"B4J is being used by our growing developer community to roll out real-world apps that solve everyday business problems faster than ever before," he said. "Based on the feedback we've received, B4J is being welcomed as an effective and long-awaited successor to Visual Basic."
the only problem is when using the .exe on a different machine due to that £$%^&* code signing thing,
Hi,
try the following links:
http://www.vbforums.com/showthread.php?t=347478
http://objectmix.com/basic-visual/156510-digital-signature-my-vb6-app.html
http://www.tek-tips.com/viewthread.cfm?qid=1319134&page=161
Hope it helps.
Regards,
A.Murugan
All part of the phaseout of COM I suppose, but the API can be used with a little more pain. It just means you'll want to do your Vista builds on XP, or at least your code-signing and possibly your MSI installer builds on XP.
All this letting alone the fact that 99% of VB6 applications wouldn't have any manifest at all...
VB6 has always been, and still is, an awesomely feature rich and most user friendly programming environment; probably the best of the kind even if not the fastest.
VB6's own engine being a transparent 100% COM solution.
Me?! No, I ain't planning to get involved in any VB6 activity in the foreseeable future. I got pretty much fed up with it in my past.
For reference, if no assembly level ComVisibleAttribute is applied, all public classes are assumed to be COM Visible. Failing to mark an assembly as [assembly: ComVisible(false)] will often result in the following Code Analysis warning, even for types that are not marked [ComVisible(true)]:
CA1405: COM visible type base types should be COM visible
Code: Visual Basic
Public Sub method1() MsgBox “Hello world” End Sub
I'm doing this to extend VB6 use since Microsoft is still willing to support it for the foreseeable future. VB6 with its user contributed enhancements works just as well or better than any other 32 BASIC out there. VB6 makes COM usable to BASIC programmers. Trying to use Roca's includes is over the heads of most. Sorry you had such a sour experience with VB6. I couldn't be happier that Dave created an SB interface rather seamless with VB6.
I find Visual Studio beyond 2008 slow, non-intuitive and difficult to use.
FYI, PowerBASIC 10.04, the latest version to date, has everything one may ever need to efficiently use early-bound (faster) COM directly in their applications.
Both VB6 and VB.NET are gonna choke with the double quotes you're using in your sources, John
Both VB6 and VB.NET are gonna choke with the double quotes you're using in your sources,
Your comment put me into a tailspin of confusion and now I'm back at square one.
Please do something with your theming support for your VB6 IDE on XP.
It seems every time I try to start VB6 IDE now, it tries to install VS2008 (again). From the few Google searches I've done this is a know problem but none of the suggested fixes worked. :-[
Do you know if it's possible with VB6 to create a forms designer?
- VB6 doesn't have a generic CONTROL widget available in FBSL/PB/TB/BCX and the like to dynamically create any common control available under Windows;
- VB6 uses extended in-house Thunder... and ThunderRT... wrappers for its set of intrinsic controls rather than raw Common Controls every other BASIC/C/whatever language uses for their UIs.
That may be true for virgin VB6 but with the use of the VBCCR13.OCX replacement for the Thunder classed controls, I don't think that is still a limitation.
I decided to do a rebuild of the Script BASIC COM extension module and was surprised how it went from zero warnings to 334.
... I should just live with the IUP dialog editor and property sheet ...
But probably I'm meddling too much in what isn't supposed to be my concern. I apologize if that is really the case. You know you are always free to trim my input to reasonable bounds if need be.
There are a zillion eye candies written in VB6 but you won't be able to use them anywhere outside Windows COM, or even look through them all in your lifetime.
Unfortunately not enough people realise that VB stands for Very Best. :)
QuoteUnfortunately not enough people realise that VB stands for Very Best. :)
QuoteQ. What is the benefit of using these over the existing controls?
Q. Does each control have the same properties? Do they have new properties?
The benefit is that these controls are linked to the comctl32.dll, that means they support the latest API calls, functions, properties and visual styles (themes).
The existing common controls 6.0 from MS are not linked to the comctl32.dll, so they doesn't support the visual styles (themes).
Reason why: The controls of the comct32.dll are compiled directly into the common controls 6.0 from MS, but as of state of a old version of comctl32.dll
Only the common controls 5.0 from MS are linked to the comctl32.dll, but the COM hull is very old and so they have a leak of the latest functions and properties. Also controls like the DTPicker, MonthView or UpDown are not included.