You would think that "Microsoft" Visual Studio 2005 would work with "Microsoft" Windows Vista without any flaws but of course it doesn't. There are several compatibility issues.
General IDE Issues
Title: Text editor insertion cursor displays incorrectly on Vista
- Description: Creating a new text file may result in the text insertion cursor failing to appear. The text files is created normally and will accept any text typed, however the cursor will not appear.
- Workaround: Insert a line break in text document and the cursor will appear.
General Debugging
Title: Script debugging will fail on launch unless internet explorer is launched as adminTitle: Remote debugging will fail due to firewall configuration
- Description: Low-rights IE does not have access to the DCOM interfaces needed for debugging with VS 2003.
- Workaround: Launch internet explorer as admin before attaching the debugger
Title: Web debugging fails due to permissions level in IE
- Description: Firewall will need to be manually configured; this is expected since VS 2003 does not automatically configure the firewall on any Operating System.
- Workaround: Please refer to How to turn on remote debugging in Windows XP with Service Pack 2, in Windows Server 2003 Service Pack 1, or in Windows Vista and Description of the DebuggerFirewall utility that makes the Visual Studio Remote Debugger work through the Windows XP Service Pack 2 firewall for configuring firewall. The KBs are for XP SP2 but the information also applies to Windows Vista.
Title: SQL Debugging not available
- Description: A developer attempting to debug a web application launches IE and browses to the application website. When putting Visual Studio into debug mode, IE will launch a new (second) instance of iexplore.exe as a low integrity process while shutting down the first instance. The debugger attaches to this first instance, which is not executing any user code.
- Workaround: Start Visual Studio with elevated administrator permissions or use the debug menu to attach to IE has been launched as admin.
Title: It is not possible to JIT Debug an elevated /privileged process
- Description: SQL Server 2005 is not supported for debugging by VS2003 on any operating system, additionally SQL Server 2000 is not supported on Windows Vista.
- Workaround: The only available SQL Server debugging style is “remote” from VS 2003 on Windows Vista targeting the SQL Server 2000 server on another operating system.
Title: IIS Configuration issues
- Description: When trying to JIT Debug, the JIT Debugger will fail.
- Workaround: None.
Visual C#
- Description: By default the Windows Vista installation of IIS does not support creation or debugging of ASP.NET 1.1 applications.
- Workaround: Follow the steps located at IIS.net : How to Enable ASP.NET v1.1 on IIS7 : Microsoft Internet Information Services to correctly configure IIS for ASP.NET 1.1 and VS 2003 debugging.
Title: ODBC Adapter Creation fails from the WizardTitle: Dataset generation for SqlDataAdapter generates errors
- Description: The DataAdapter wizard can cause Visual Studio to hang after clicking on the "New Connection" button.
- Workaround: None.
Visual Basic
- Description: Generating a dataset for sqlDataAdapter will cause an error message about the DataAdapter not being configured to show multiple times.
- Workaround: Keep selecting OK on the error message dialog box; the wizard eventually proceeds to create a dataset successfully.
Title: WebForms Dynamic Help fails for HTML ControlsTitle: Dynamic Help does not display the help contents when HTML controls or tags are selected
- Description: In some cases no dynamic help for HTML controls will display in the Web Forms Designer
- Workaround: None.
Title: User controls may appear to not upgrade correctly
- Description: When a developer selects a control or tag from a web form the Dynamic Help Window does not display help links for various controls and tags.
- Workaround: None.
Title: Web classes fail on Windows Vista
- Description: When upgrading a Visual Basic 6.0 application, user controls may appear to upgrade incorrectly but when the project is executed the application runs properly.
- Workaround: None.
Web Forms
- Description: Web classes will fail due to fundamental changes in the behavior of IIS 7.
- Workaround: None.
Title: Debugging an ASP.NET applications failsVisual C++
- Description: After creating a web application in cPanel® a developer attempts to debug the application and receives the “cannot start ASP.NET or IIS debugging” failure dialog from Visual Studio.
- Workaround: The DEBUG verb may not be registered with the ASPX handler. Register the DEBUG verb with the ASPX handler to enable debug to automatically start.
Title: General recommendations for running Visual C++ and user created applications on Windows Vista
- Description: The Visual C++ IDE and user created deployment packages need elevated permissions.
- Workaround: Currently there are no known issues if the Visual C++ IDE and user created deployment packages are run with elevated administrator permissions.
Ow, huge list. Well it's Microsoft, I thought that everything worked like XP and more, well seems I was wrong!
I view Vista as the ultimate IT department nightmare. Managers will want it and IT will hate it.
I agree. It has a lot of problems that need to be fixed.
Learning Programmer
Why not use Microsoft Visual Studio 2008? It's compatible with 2005. And I tried installing visual basic 6 in Vista (yowzers) but when loading components vista spat out some errors. Oh, and has anyone tried Windows 7?
Yes , search in forum .. is a thread about WINDOWS 7 ...Originally Posted by Martin_kp
And this is a very old thread, so please do not revive it Martin_Kp.
End of discussion here, continue in another (recent) thread.
Yup, this was posted in the first month of 2007.... Before Visual Studio 2008.
Well, lock it then!
There is no rule against reviving dead threads.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
LinkBack URL
About LinkBacks
Bookmarks