Visual Studio 2005, codenamed Whidbey (a reference to Whidbey Island in Puget Sound),
was released online in October 2005 and to retail stores a few weeks
later. Microsoft removed the ".NET" moniker from Visual Studio 2005 (as
well as every other product with .NET in its name), but it still
primarily targets the .NET Framework, which was upgraded to version 2.0.
It is the last version available for Windows 2000 and also the last version to be able to target Windows 98, Windows Me and Windows NT 4.0 for C++ applications.
Visual Studio 2005's internal version number is 8.0 while the file format version is 9.0. Microsoft released Service Pack 1 for Visual Studio 2005 on 14 December 2006. An additional update for Service Pack 1 that offers Windows Vista compatibility was made available on 3 June 2007.
Visual Studio 2005 was upgraded to support all the new features
introduced in .NET Framework 2.0, including generics and ASP.NET 2.0.
The IntelliSense
feature in Visual Studio was upgraded for generics and new project
types were added to support ASP.NET web services. Visual Studio 2005
also includes a local web server, separate from IIS, that can host ASP.NET applications during development and testing. It also supports all SQL Server 2005 databases. Database designers were upgraded to support the ADO.NET 2.0, which is included with .NET Framework 2.0. C++ also got a similar upgrade with the addition of C++/CLI which is slated to replace the use of Managed C++.
Other new features of Visual Studio 2005 include the "Deployment
Designer" which allows application designs to be validated before
deployments, an improved environment for web publishing when combined
with ASP.NET 2.0 and load testing to see application performance under
various sorts of user loads. Starting with the 2005 edition, Visual
Studio also added extensive 64-bit support. While the host development
environment itself is only available as a 32-bit application, Visual C++
2005 supports compiling for x86-64 (AMD64 and Intel 64) as well as IA-64 (Itanium). The Platform SDK included 64-bit compilers and 64-bit versions of the libraries.
Microsoft also announced Visual Studio Tools for Applications as the successor to Visual Basic for Applications (VBA) and VSA (Visual Studio for Applications). VSTA 1.0 was released to manufacturing along with Office 2007.
It is included with Office 2007 and is also part of the Visual Studio
2005 SDK. VSTA consists of a customized IDE, based on the Visual Studio
2005 IDE, and a runtime that can be embedded in applications to expose
its features via the .NET object model. Office 2007 applications
continue to integrate with VBA, except for InfoPath 2007 which
integrates with VSTA. Version 2.0 of VSTA (based on Visual Studio 2008)
was released in April, 2008. It is significantly different from the first version, including features such as dynamic programming and support for WPF, WCF, WF, LINQ, and .NET 3.5 Framework.
Supported .NET Framework versions: 2.0, 3.0
The product was released 2005-11-07.
Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results (selected in 'Test Results' table below)
What works
Setup, compiling, linking, IDE, the whole 9 yards.
What does not
Some installer bugs prevent full IDE installation; certain projects (class library, etc) cannot be created.
"Finish" button hangs at new project window.
What was not tested
C#, J#, SQL, MFC, other kinds of projects.
Some Microsoft debuggers fail to enumerate processes due to wtsapi32.WTSEnumerateProcessesW() being a stub (Microsoft Visual Studio 2005, DbgCLR from .NET 2.0 SDK)
After IDE start, the start page constantly refreshes, eating CPU
This is bug 10522. Close the "Start page" to work around this problem.
Installing Visual Studio 2005 component action takes considerable time (consuming 100% CPU)
This is bug 14168. The installer takes considerable time when the Installing Visual Studio 2005 component is processed on install page. Depending on machine speed it takes 20-60 minutes until it really
begins to copy files.
Wine's msi component executes large
table joins which causes this performance hit (CPU usage 100% for long time). Just be patient.
Components displayed which failed installation in finish installation setup page
In the "finish installation" setup page of the VS.NET 2005
Enterprise version, there are components displayed which failed installation. This can be currently ignored (needs further investigation).
Microsoft Device Emulator 1.0
Microsoft SQL Server 2005 Express Edition
err:module:import_dll Library sqdedev.DLL not found
The following installer message in console is expected and harmless:
err:module:import_dll Library sqdedev.DLL (which is needed by L"C:\\windows\\temp\\msi3a93.tmp") not found
err:msi:ACTION_CallDllFunction failed to load dll L"C:\\windows\\temp\\msi3a93.tmp"
Compiler gets stuck during code generation (PDB server)
You can create a shell script that starts both mspdbsrv.exe and
VCEXpress.exe, if mspdbsrv.exe is already running, it will be ignored
the second time it is invoked.
/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 things 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.
