Andreas Mohr wrote:
I keep encountering people mentioning that VB stuff has lotsa problems on Wine. While I really can't say that I like VB, a lot of people seem to use it for critical tasks in companies on a daily basis, so it sounds like perfect VB compatibility would be utterly important. IMHO improving that should be a goal of 0.8.
Make sense. How about this: let's add a visual basic regression test suite to Wine.
I'm not kidding! Ought to be pretty easy to hit at least the non-gui parts...
- Dan
Make sense. How about this: let's add a visual basic regression test suite to Wine.
I'm not kidding! Ought to be pretty easy to hit at least the non-gui parts...
I think this is a great idea. It will be a bit challenging - my understanding is that most VB apps that people want to use in production are database apps, and so the trick is also making sure that the various database engine flavors work as well.
Also, there have to be at least one or two freeware Visual Basic programs that could be stashed somewhere as reference programs for use in regression testing.
Jer
On Fri, 8 Nov 2002, Dan Kegel wrote:
Andreas Mohr wrote:
I keep encountering people mentioning that VB stuff has lotsa problems on Wine. While I really can't say that I like VB, a lot of people seem to use it for critical tasks in companies on a daily basis, so it sounds like perfect VB compatibility would be utterly important. IMHO improving that should be a goal of 0.8.
Make sense. How about this: let's add a visual basic regression test suite to Wine.
I'm not kidding! Ought to be pretty easy to hit at least the non-gui parts...
It's nice to make a Wine regression test suite in Visual Basic. But how are you going to get the VB applications compiled on Linux?
It seems to me that this regression test suite will only be usable on Windows and that one will have to copy the binaries to a Linux machine to actually do any testing. In that case, wouldn't it be better to keep it as a separate project (separate CVS, etc.) altogether?
Francois Gouget wrote:
It's nice to make a Wine regression test suite in Visual Basic. But how are you going to get the VB applications compiled on Linux?
By running Visual Basic under Wine, of course. Can't we do that? Even if not everyone can do that, that's ok; not everyone has to compile the test. We want the compiled test to be run nightly along with the C/C++ regression test, IMHO. So I don't see any reason to separate it from the Wine regression test.
I do kinda see a good reason to separate all the regression tests out from the Wine tree, though: there are many implementations of Win32, and all of them can benefit from having a common win32 regression test. So I'd happily go along with keeping the VB regression test out of the Wine tree if we did the same with the C/C++ regression test...
- Dan
This would be the first testcase that could involve a winedbg call. :)
By running Visual Basic under Wine, of course. Can't we do that? Even if not everyone can do that, that's ok; not everyone has to compile the test. We want the compiled test to be run nightly along with the C/C++ regression test, IMHO. So I don't see any reason to separate it from the Wine regression test.
I do kinda see a good reason to separate all the regression tests out from the Wine tree, though: there are many implementations of Win32, and all of them can benefit from having a common win32 regression test. So I'd happily go along with keeping the VB regression test out of the Wine tree if we did the same with the C/C++ regression test...
___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
On Fri, 8 Nov 2002, Francois Gouget wrote:
On Fri, 8 Nov 2002, Dan Kegel wrote:
Andreas Mohr wrote:
VB compatibility would be utterly important. [...]
Make sense. How about this: let's add a visual basic regression test suite to Wine. [...]
[...]
In that case [seperate binaries], wouldn't it be better to keep it as a separate project (separate CVS, etc.) altogether?
How about adding this to WRT?
It should be fairly easy to add extra tests (such as running binaries) to the conformance testing. Especially if the VB executables terminate themselves.
---- Paul Millar
To demonstrate some important VB problems I made a few VB test apps. Those test apps are located at http://www.xs4all.nl/~sailsup/wine-vb.tar.gz
The package contains some database applications using various MS database implementations (DAO, ADO), two simple tests. Next to this the package contains one of those tests combined with a VB installer application.
To run these apps the VB 6.0 runtime library should be installed and perhaps dcom98. The app that is bundled with an installer contains the vb runtime library and most of the files from dcom98 I think. (get dcom98 from here if you need it: http://www.microsoft.com/com/dcom/dcom98/download.asp)
Now I will tell about problems when running those very basic apps. I'll start with the app with installer. When this app starts the installer, the installer first tries to install parts of the VB 6.0 runtime and some other files. It crashes somewhere during the extraction of the files. (I think it crashes because builtin oleaut32.dll is used and not the to be extracted native oleaut32.dll). When installing dcom98 before running this setup the setup app still doesn't run, but when you tell wine to use native oleaut32 from dcom98 it works fine.
After the app is installed, it doesn't runIt crashes while loading the activex database control which is needed for this app and then launches winedbg. (control is installed by the setup)
After this there are two very simple apps one containing only an empty form and one containing a button on a form that run well. The only minor problem is in the button app. When you click on the button it should show a messagebox containing a text. On windows the text in the messagebox is alligned to the left or perhaps to the center, but on wine the text is alligned to the right. (looks ugly)
Next to these two simple apps there are three database apps (db1, db2 and db3). (one of them called db2 is the one bundled with the setup package) Neither of those apps works well. These apps report various errors "runtime error 335: can't access the system registry" and more of this crap.
I ran all these apps on a Wine CVS version which I compiled about two weeks ago. My wine install was clean. I started with a fresh fake c: drive and a fresh wine registry (imported from winedefault.reg ofcourse). The problems on my test apps seem to be related to missing functionality in wine builtin dlls, problems with registering activex controls, registry problems and more.
I hope these simple apps already help a lot. Most VB problems are very similar to these. If more and better tests are needed, just ask.
Roderick Colenbrander
-
Dan Kegel -
Francois Gouget -
Jeremy White -
Paul Millar -
Roderick Colenbrander -
Sylvain Petreolle