Useing MSVBVM50.DLL in Nasm

[TheToastIsALie]

Can i use MSVBVM50.DLL in executables made with Netwide Assembler
There May Be some Copyright issues And better ways to do it But Can It be done?

For Example Loading An Active X Ocx With GUID,File Name & Control name

can this be done useing MSVBVM50.DLL On an Exe produced Using Netwide Assembler

[Frank Kotler]

I don't see why not. I can't imagine it requires any instructions that Nasm doesn't know.

Best,
Frank

[TheToastIsALie]

Thank you i think i will Try useing  MSVBVM50.DLL in a Nasm Executable
the reason why i asked is because I am making a program that gets Info from Vb5 forms
And i plan to use Nasm To produce Executables with this information

it will use the layout information to produce source code
it is mostly doing the layout and controls and it does not convert code yet
if i use MSVBVM50.DLL it could save some time
but all my program can do at this time is get the width,height,left,top &other properties of the form and its controls
and it also can convert them to pixels if needed

[Bryant Keller]

Shameless Plug Follows 

Being that you don't mind having users install extra DLL's into Windows... You might think about using GTK/Glade interface files. They are basically XML files which make them really easy to work with (and Glade UI designer is fairly simple as well). The UI will work on pretty much any OS (Linux, Windows, BSD, etc) as long as the user has the GTK/Glade runtime library installed. And whats more, I've already distributed a neat little tool (open source and tested on Linux) which you can play with porting to Windows if you feel so inclined. This tool is Glade2Nasm(FE), it takes the *.glade file as input and generates a .asm source with the signals you've assigned prepped as procedures that you can fill in with your code. Using the Glade2Nasm(FE) I was able to create a quick NASM hello world application (with a single button control that launches my website in the default browser) in 9 seconds, so consider this a RAD tool.

Glade2Nasm(FE) http://assembly.ath.cx/code/g2nasm.tgz

WARNING The code generated by this application is NOT optimized at all. The generated code is only designed to work and it has only been tested on GNU/Linux. Of course, the source code for the application is extremely simplistic (for good reason) to allow users to modify the generated code to their own tastes (I suggest you do that).

Regards,
Bryant Keller

[TheToastIsALie]

I think there is a Vb to Glade
the aim is to make a vb frm to exe tool
but vb projects that use ActiveX and windows only technology's would require extra software

so i could add multiple ways of creating executables
if a vb project has used only the default vb controls with no active x it could be used to make platform independant code to be compiled on multiple OS

so
method 1 create exe useing MSVBVM50.DLL
method 2 create exe without useing MSVBVM50.DLL

method 3 create source code that can be compiled on non Win/Ros operating system
but only if no windows only technology's are used if they are used it will have to use something like wine to use them
but if id did use wine or something else method 3 would be pointless

so method 3 will only compile if the vb project uses no dlls or ocxs

but this program would be complex so i think havening 2 versions

my project limitations
it can only convert vb projects that have only 1 form but not mdi forms
it will not convert complex vb projects
it is not going to be able to do much in the first few versions
Gui apps only

what i plan to make
it is a wizard that looks like iexpress
it will open vb frm files not vbp because of its limitation
it will get information from the frm files
-Here is the part i don't have yet-
it will use the extracted information to make nasm source code

when i have fixed some major bugs and added some source code creation functionality i will post it on the internet with the source code

But i will note that the point of this is to create a vb5 exe generator
that produces exe files that are simalar to those produced with vb5
the reason for useing MSVBVM50.DLL is because it is bundled with most windows OS although some have only MSVBVM60.DLL

also MSVBVM60.DLL contains most if not all functionality of MSVBVM50.DLL so if i use MSVBVM50.DLL you also have the option of MSVBVM60.DLL

its going to be a while before i have something that works

The targeted os is windows 95,nt4,98/98SE/ME,2000,XP & REACT Os