Visual Studio

From Wine-Wiki

Jump to: navigation, search

Visual Studio is used by many..

Contents

Wine Application Database

As of Feb 2009


This Software is listed in the Official Wine Application Database

Winehq Main AppDB entry Visual Studio Express

  • Winehq AppDB entry Visual express 2005 One Maintainer. rated as bronze with a recent version of wine. More testers are needed for the express version.
  • Winehq AppDB entry Visual express 2008

As of Feb 2009 this is improving as the blocking bugs are mostly known.


This Software is listed in the Official Wine Application Database

Winehq Main AppDB entry Visual Studio .Net


This Software is listed in the Official Wine Application Database

Winehq Main AppDB entry Visual Studio

  • Winehq AppDB entry Version 6 Enterprise rated barely usable.
  • Winehq AppDB entry Version 6. this may be a dup. rated gold with older versions of wine. needs more recent tests.
  • Winehq AppDB entry Version 6 Standard. rated bronze with very old version of wine. needs more recent tests


This Software is listed in the Official Wine Application Database

Winehq Main AppDB entry Visual C

Winehq AppDB entry Version 6 rated highly with known bugs identified.

  • Can you add your results to the Official Wine Appdb? Submitting your results for this software under Wine will help the many other users who run Wine.
Become a Maintainer
Have you considered volunteering to be an additional Maintainer for this software.

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.

  • Who can be a Maintainer? - anyone. no programming experience required.
  • What is required of a Maintainer? - not much, but you do make a real difference.

Official Information

Unofficial Information

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.

  • This often results in very quick fixes.

Further Help to Wine
If you are able to keep an eye out for bug reports for your software and adding a note to the bug report whether you can confirm if it is a real bug or not, you can help the bugzilla team and developers spend more time on improving Wine. For each Wine release, make a small note in the bug confirming whether it is still present or if it has been fixed.


Forum Comments

Visual express 2005 not installing bug 5054 was marked FIXED in Jan 2009 - it now installs.. You may remember it was in Jul 2007 wine devel that list comments reported it as only installable by copying over from windows install. Quite a bit of progress has been made in wine as shown by bug 56365 (possibly the only bug blocking vs net 2003)

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 {{winebug|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 Winehq Bugzilla entry 3846

R. Shearman [May 06]: Winehq Bugzilla entry 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: 

$ 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 64

Links

Wine Links

(Official) Wine Links

(Unofficial) Wine-Wiki Links


External Links

Retrieved from "http://wiki.jswindle.com/index.php/Visual_Studio"
Personal tools