WineHQ

Visual Studio

No Screenshot

Submit Screenshot

Microsoft released Visual Studio .NET (VS.NET), codenamed Rainier (for Washington's Mount Rainier), in February 2002 (the beta version was released via Microsoft Developer Network in 2001). The biggest change was the introduction of a managed code development environment using the .NET Framework. Programs developed using .NET are not compiled to machine language (like C++ is, for example) but instead to a format called Microsoft Intermediate Language (MSIL) or Common Intermediate Language (CIL). When a CIL application executes, it is compiled while being executed into the appropriate machine language for the platform it is being executed on, thereby making code portable across several platforms. Programs compiled into CIL can be executed only on platforms which have an implementation of Common Language Infrastructure. It is possible to run CIL programs in Linux or Mac OS X using non-Microsoft .NET implementations like Mono and DotGNU.

This was the first version of Visual Studio to require an NT-based Windows platform. The installer enforces this requirement.

Visual Studio .NET 2002 shipped in four editions: Academic, Professional, Enterprise Developer, and Enterprise Architect. Microsoft introduced C# (C-sharp), a new programming language, that targets .NET. It also introduced the successor to Visual J++ called Visual J#. Visual J# programs use Java's language-syntax. However, unlike Visual J++ programs, Visual J# programs can only target the .NET Framework, not the Java Virtual Machine that all other Java tools target.

Visual Basic changed drastically to fit the new framework, and the new version was called Visual Basic .NET. Microsoft also added extensions to C++, called Managed Extensions for C++, so .NET programs could be created in C++.

Visual Studio .NET can produce applications targeting Windows (using the Windows Forms part of the .NET Framework), the Web (using ASP.NET and Web Services) and, with an add-in, portable devices (using the .NET Compact Framework).

The Visual Studio .NET environment was rewritten to partially use .NET. All languages are versions of Visual Studio, it has a cleaner interface and greater cohesiveness. It is also more customizable with tool windows that automatically hide when not in use. While Visual FoxPro 7 started out as part of Visual Studio .NET 2002, and early VS betas allowed debugging inside VFP-based DLLs, it was removed before release to follow its own development track.

The internal version number of Visual Studio .NET 2002 is version 7.0.


Supported .NET Framework versions: 1.0


The product was released 2002-02-13.

Service Pack 1 for Visual Studio .NET 2002 in March, 2005

Application Details:

Version: 2002 (7.0)
License: Retail
URL: http://www.visualstudio.net
Votes: 0
Latest Rating: Garbage
Latest Wine Version Tested: 1.1.13

Maintainers: About Maintainership

Free Download http://www.visualstudio.net/

Test Results

Old test results
The test results for this version are very old, and as such they may not represent the current state of Wine. Please consider submitting a new test report.
Selected Test Results

What works

Nothing due to installer blockers.

What does not

n/a

Workarounds

What was not tested

n/a

Hardware tested

Graphics:

  • GPU:
  • Driver:

Additional Comments

Just for historical purpose and for tracking bugs.

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
Workaround?
RatingSubmitter
CurrentFedora 10 x86_64Jan 25 20091.1.13No Not installable GarbageAnastasius Focht 

Known Bugs

Bug # Description Status Resolution Other apps affected
8439 Multiple Microsoft product installers fail due missing shell app path expansion (Visual Studio .NET 2002, 2003, Visual Foxpro 9.0) NEW View

Show all bugs

HowTo / Notes

HOWTO

Make sure you operate on a clean 32-bit WINEPREFIX (~/.wine)!


1. Prerequisite installation by using 'winetricks' script­

Winetricks will take care of all needed installation prerequisites and work around some problems.

$ wget http://winetricks.googlecode.com/svn/trunk/src/winetricks
$ bash winetricks -q gecko vcrun6 vb6run jet40

Optionally install core fonts

$ bash winetricks corefonts
­

2. Apply a patch­

See "Work­around for bug 8439 (setup disappears)" note for HOWTO.­ After that you can use the installer.

/home/yourlogin/.wine is not owned by you / (Permission denied)
­­­

­­Never run wine as root (su, sudo)! Wine doesn't require to be run as root!

You will screw your WINEPREFIX and possibly other thi­ngs up. If you have run Wine as root you need to:

$ sudo rm -rf ~/.wine­

and then run winecfg to set Wine folder structure back up. If you used winetricks script as root you might also need to:

­$ sudo rm -rf ~/winetrickscache

Again: Just run wine as regular user and all should be fine.

­­
Workaround for bug 8439 (setup disappears)

To work around the disappearing installer, described in bug 8439, yo­u must compile and install Wine from source after applying the following patch. Refer to Wine User Guide "Installing Wine from Source" here.

1.) Save the following snippet to a text file: Patch­

2.) Apply the patch (cd to Wine source tree first):

[wine-source]$ patch -p0 < wine-shell32-execute.patch

3.) ­Compile Wine and install.

Now you can run the installer.

Comments

Back