Visual Studio
From Wine-Wiki
Visual Studio is used by many..
Contents |
Wine Application Database
- http://appdb.winehq.org/appview.php?iVersionId=4813 Visual express 2005.
- Wine Application Database entry for Visual Studio 2003
- Wine Application Database Entry for Visual Studio 7
- Please consider submitting your test results for running this software under Wine.
| |
Regularly Submitting results for installing and running on the latest version of Wine makes a big difference for others considering using Wine. By looking at how well the software runs others can be encouraged to try it themselves and together you can make progress in finding workarounds. By testing the software you will also notice when something breaks and when you make a bug report, the bugzilla team will often point it out to the person who broke it. If you are slightly more technically minded, you are able to regularly compile wine and test it before each fortnightly release then you will catch breakages before each wine release.
A big advantage of being a maintainer is that as you quickly become familiar with installing and using wine with your software, you can have a direct hand in improving wine and your software. Many times you will find very handy tips posted by others and by posting a summary many benefit from your work. When you are asked a question you don't know, simply post in the wine-users forum and perhaps someone can help. Just by being there, you make a difference. A maintainer quickly tests each monthly release of wine, and adds to the application database a rating of how good it runs.. gold/silver/bronze or garbage. Wine is constantly being improved, and occasionally something breaks. When you do spot a breakage, file a bug in bugzilla and if you want to try and fix it you can then post to the wine-devel mailing list for advice. However, if you have a little spare time (usually about 2 hours, in between doing other things) regression testing allows you to identify which patch caused the break. By filling out a bugzilla report, posting the name of the software, and the patch which broke it to the wine-devel mailing list, the developer who broke it can have a look at fixing it.
|
Forum Comments
Visual express 2005. Jul 2007 wine devel list reports as installable by copying over from windows install.
Compiling VB Apps under Wine
Villaci-s Lasso [June 06]:People who manage to compile VB apps under Wine with VB6 are likely to stumble upon this bug (at least under GNOME/Metacity): Bug 1598 - delphi 3 - managed - missing minimize/maximize buttons http://bugs.winehq.org/show_bug.cgi?id=1598 In addition, if anyone tries to use DBGRID32.OCX, they will surely hit this bug: Bug 3846 - Wine can't run Roderick Colenbrander's DBGRID32.OCX VB test apps yet http://bugs.winehq.org/show_bug.cgi?id=3846
R. Shearman [May 06]: http://bugs.winehq.org/show_bug.cgi?id=3846 This should be fixed as of today. wine archive
To do that you need to copy the files :
- msvcmon.exe
- msvcr70.dll
- NatDbgDM.dll
- NatDbgTLNet.dll
under a directory on Linux execute
wine msvcmon
And everything works like if you were debugging remotely a windows application
Building 64 bit dll
A programmer reported [Jun 07 wine user]: I installed VS Express and included the IDE in $LIB. It looks like wine is able to run 'cl.exe' but 'cl.exe' itself has a problem. We've tried a number
of variations of setting %TMP% and %TEMP% to no avail.Any ideas.
M. Dontu [wine user jun 07] I don't know if this is of any use anymore, but I've had the same problem and google did not have the answer (because no one posted/mailed it). So this one is for Google. What I did: I installed PSDK for Windows 2k3 (in Windows) and then, from Linux, I copied the whole contents of %A_VS_DIR%/bin into ~/apps/vs64/bin. Then in ~/bin I've put a small script like this:
#!/bin/sh
wine "${HOME}/apps/vs64/bin/cl.exe" "${@}"
first attempt:
$ make -f makefile.win64 cl64 /c /nologo /TC /Wall /Wp64 /MD /Zi /Gd /Od /I. /D__WINDOWS__/D__WIN64__ /I/home/user/apps/vs/include /Fo_stricmp.o _stricmp.c cl :Command line error D8037 : cannot create temporary il file; clean temp directory of old il files make: *** [_stricmp.o] Error 2
[after more work he then did...]
$ export WINEDEBUG=relay # this feature rocks too much! $ make -f makefile.win64 1>cl64.log 2>&1 $ less cl64.log HKEY_LOCAL_MACHINE/Software/Microsoft/Cryptography/Defaults/ProviderTypes/Type 001 => Name = "Microsoft Strong Cryptographic Provider" (REG_SZ) HKEY_LOCAL_MACHINE/Software/Microsoft/Cryptography/Defaults/Provider Types/Type 001 => TypeName = "RSA Full (Signature and Key Exchange)" (REG_SZ) HKEY_LOCAL_MACHINE/Software/Microsoft/Cryptography/Defaults/Provider/Microsoft Strong Cryptographic Provider => Image Path = "rsaenh.dll" (REG_SZ) HKEY_LOCAL_MACHINE/Software/Microsoft/Cryptography/Defaults/Provider/Microsoft Strong Cryptographic Provider => SigInFile = "0x00000000" (REG_DWORD) HKEY_LOCAL_MACHINE/Software/Microsoft/Cryptography/Defaults/Provider/Microsoft Strong Cryptographic Provider => Type = "0x00000001" (REG_DWORD)
[...] I hope this will be of some help to someone.
When asked for further information he replied: I needed to build a 64bit dll that was to be used in a Linux app (via a win64 emulation layer). Since I only have my laptop, I did not want to switch from Linux to Windows all the time and I decided to make cl.exe and link.exe work on wine.
What I did was:
- while in Windows, I downloaded and installed the PSDK from here: http://www.microsoft.com/downloads/details.aspx?FamilyId=0BAF2B35-C656-4969-ACE8-E4C0C0716ADB&displaylang=en
- switched to Linux and _read_ the instructions here: http://msdn2.microsoft.com/en-us/library/ms235291(VS.80).aspx (they offer some insights about that needs to be copied and/or installed)
- then:
$ mkdir -p ~/apps/vs64/bin; $ cp -R /media/hda1/Program\ Files/Microsoft\ Platform\ SDK\ for\ Windows\ Server\ 2003\ R2/Bin/win64/x86/AMD64/* ~/apps/vs64/bin;
- you will need to copy in ~/apps/vs64/bin some other dll-s like: $ # msdis150.dll, msobj80.dll, mspdb80.dll, msvcp80.dll, msvcr80.dll, pgodb80.dll, pgort80.dll (if they're not already there)
- from the redistributable 64bit packages, you'll need: "Microsoft.VC80.CRT" and "Microsoft.VC80.MFC", which will go in bin too
$ mkdir -p ~/apps/vs64/include $ cp -R /media/hda1/Program\ Files/Microsoft\ Platform\ SDK\ for\ Windows\ Server\ 2003\ R2/Include/* ~/apps/vs64/bin;
- merge the registry keys attached
- set the TMP environment variable to something simple (C:\WINDOWS\TEMP)
$ mkdir ~/bin
$ cat >~/bin/cl
#!/bin/sh
wine "${HOME}/apps/vs64/bin/cl.exe" "${@}" ^D
$ chmod +0755 ~/bin/cl
$ cat >~/bin/link
#!/bin/sh
wine "${HOME}/apps/vs64/bin/link.exe" "${@}" ^D
$ chmod +0755 ~/bin/link
The paths to libraries and include files are given by me my explicitly, that's because I need things under strict control (don't want cl.exe to assume anything) - so I have no env for you :) This should do (unless I forgot something) :). I was pressed by time and I did not "take notes" of all the steps I did (I've build myself a tarball with all that and this will be my future VS 2k5 64bit).
Links
