När jag kör ett asp.net program i VS2005 och vill avsluta körningen så stoppas inte programmet då jag stänger ned förnstret via "X" knappen
Fönstret blir kvar men blir tomt och bara vägrar försvinna
I Debugg läget måste jag välja "Stop Debugging" för att avsluta körningen
I läget utan debugg går det inte alls.

Fönstret är IE V7.0

Detta har tidigare fungerat men något har blivit fel eller någon inställning.

Vore tacksam för tipps hur jag ska åtgärda.


mvh Roland

Kör du Vista?

Hittade en generell lista med tänkbara fel som händer mellan Visual Studio 2005 och Windows Vista, kanske något står där: http://msdn2.microsoft.com/en-us/vs2005/aa964140.aspx


General

Add Reference dialog does not show a help button on title bar
Active Directory Deployment of Visual Studio 2005 fails on Windows Vista
Exiting VC# Express may cause application crash
Files double-clicked in Windows Explorer may not open automatically in Visual Studio
Some command line switches require administrative permissions
The Visual Studio Team Foundation Team Build option will not install on Windows Vista unless IIS is present
When installing any Visual Studio Express product the BITS download service will fail due to permission issues.
Visual Studio products fail to install in XP compatibility mode.
Upgrading to Windows Vista may result in loss of New Project Dialog templates
Opening the Add-in/Macros Security option in the Tools dialog will hang Visual Studio
Just-In-Time (JIT) Debugging of an elevated process will fail
Office

Browse web services on local machine
Catching exception with the debugger is slow
Attaching/detaching with the profile may stop producing results
Smart Devices

“Not enough storage” error occurs when you open Property Pages in Japanese versions of Visual Studio
After upgrading to Windows Vista upgrade, the New Project dialog names for Windows Mobile 5.0 nodes are changed for managed projects.
Visual Studio fails to create native C++ projects
Using Remote Tools on Windows Vista
Cannot Cradle the Emulator in Windows Vista
Device Emulator Manager (DEM) UI Corrupted when aborting the emulator
SQL Server Mobile Edition databases created on Windows XP or older operating systems (and device emulators) do not work on Windows Vista and vice versa.
Web

Dataset Designer extremely slow on Windows Vista
Browse web services on local machine may fail without the IIS6 Compatibility Layer installed
Creating a new website for IIS 7 generates misleading error messages
Localhost tab of Open Website provides misleading error messages under default install of IIS 7
Opening a web solution with many sites is much slower on Windows Vista
Visual Studio fails to set permissions on App_Data folder
Using FTP connections in Visual Studio on a Windows Vista Client frequently fails
Attaching/detaching with the profile may stop producing results
ASP.NET Unit tests may fail with IIS running on Windows Vista
Debugging Web applications on IIS may fail without the IIS 6 Compatibility Layer installed
Users are unable to install Web setup MSI on Windows Vista
Using FTP connections in Visual Studio on a Windows Vista Client frequently fails
Windows

Dataset Designer extremely slow on Windows Vista
Browse web services on local machine may fail without the IIS6 Compatibility Layer installed
Media Player OCX control does not work in tool windows created with CreateToolWindow()
Project imports for Windows Workflow Foundation result in unexpected security warning
Some SDK Tools may not run as expected
Visual Studio crashes when deleting menu items with sub menus
SDK Quickstart configuration fails
Attaching/detaching with the profile may stop producing results
Trace profiling fails on a managed C++ console application
Launching the vsjitdebugger with a process name fails on Windows Vista
Code coverage binaries are not marked as 32-bit only causing them to crash on wow64
Debugger hangs while debugging openmp parallelized for loop
Setting up remote debugging fails to configure the firewall on Windows Vista
Remote Debugger fails or is unusable on Windows Vista Starter Edition
Developers will be unable to set RPC stepping as administrator



General
Title: Add Reference dialog does not show a help button on title bar

Description: When you open the Add Reference dialog there is no visible help button. The functionality exists but the UI element is missing.
Workaround: Press F1.

Title: Active Directory Deployment of Visual Studio 2005 fails on Windows Vista

Description: When a corporation deploys Visual Studio to their developer desktops using the Active Directory deployment scenario (as described here) the setup will fail because it tries to install the .NET Framework 2.0 which is already installed on Windows Vista.
Workaround: Manually remove the check for the .NET Framework as documented in Section 5.3 of the Enterprise Network Deployment Readme. This section is located here.

Title: Exiting VC# Express may cause application crash

Description: An AccessViolation may occur while exiting Visual C# Express.
Workaround: None. Ensure that you save all your work prior to exiting Visual C# Express.

Title: Files double-clicked in Windows Explorer may not open automatically in Visual Studio

Description: When a user double-clicks on a Visual Studio associated file in the Windows Explorer, Visual Studio may only launch and not open the file. Double-clicking on them a second time will open the file in Visual Studio.
Workaround: Open file from within Visual Studio, or double-click twice on it

Title: Some command line switches require administrative permissions

Description: The DevEnv.exe command line switches /setup, /installvstemplates, and /associatefiles require administrative permissions for proper operation. Invoking these commands from without elevated administrator permissions could result in data loss.
Workaround: Run a command window with elevated administrator permissions and then start DevEnv.exe with the required command line switch.

Title: The Visual Studio Team Foundation Team Build option will not install on Windows Vista unless IIS is present

Description: In order to build Web projects Team Build must have permissions to compile ASP.NET apps. The current Team Build setup configures these permissions via a call to aspnet_regiis. On Windows Vista this call fails when IIS is not present and this causes setup to fail and perform a roll-back.
Workaround: Customer must install IIS before installing Team Build. Since IIS is not necessary they may uninstall it after Team Build is installed.

Title: When installing any Visual Studio Express product the BITS download service will fail due to permission issues.

Description: Visual Studio Express Editions use the BITS service to download the install packages. Anyone attempting the install will need to give elevate administrator permissions to the setup utility to run it. However these elevated permissions do not flow onto BITS so the download fails when a standard user runs as admin.
Workaround: Manually download the install files as described here or run the install from an account with administrative permissions.

Title: Visual Studio products fail to install in XP compatibility mode.

Description: All Visual Studio products will fail to install with an error message saying “You need to install Windows XP SP2 before you install Visual Studio”. This happens due to the way detection logic is structured. We do not recommend installing VS in compatibility mode and there is no workaround to this scenario.
Workaround: None

Title: Upgrading to Windows Vista may result in loss of New Project Dialog templates

Description: After upgrading to Windows Vista, various project templates in the New Project dialog may be missing.
Workaround: Open an command prompt with elevated administrator permissions and run the command “devenv.exe /installvstemplates.”

Title: Opening the Add-in/Macros Security option in the Tools dialog will hang Visual Studio

Description: When a user opens the tools dialog and then selects the Add-in/Macros leaf of the Environment node, Visual Studio will hang.
Workaround: None

Title: Just-In-Time (JIT) Debugging of an elevated process will fail

Description: Elevated processes cannot be JIT Debugged by VS 2005. This includes system processes, such as IIS, and applications started by selecting ‘Run as administrator’.
Workaround: The debugger must be attached manually before the debugger will catch unhandled exceptions or user break points (System.Diagnostics.Debugger.Break, __debugbreak, etc).


>Return to Top of Page


--------------------------------------------------------------------------------

Office
Development

Title: Browse web services on local machine

Description: Attempting to browse the local machine for web services will generate the following error message:
There was an error while enumerating services on local machine:
Active Directory Services cannot find the web server. A possible cause for this is an incompatibility between versions of Internet Information Server (IIS) on the client and the server. Another possible cause is that IIS is not installed on the local machine, or the user identity under which you are running may not have permissions to view websites on this machine.
Workaround: You will need to run Visual Studio with elevated administrator permissions.

Debugging

Title: Catching exception with the debugger is slow

Description: When user code generates an exception the debugger may perform slowly in catching the exception.
Workaround: None. The exception will be caught it may just take some time.

Title: Attaching/detaching with the profile may stop producing results

Description: Occasionally the profiler may stop producing results when the developer attaches and detaches it from a process.
Workaround: None. Shut down Visual Studio and restart it.


>Return to Top of Page


--------------------------------------------------------------------------------

Smart Devices
Development

Title: “Not enough storage” error occurs when you open Property Pages in Japanese versions of Visual Studio

Description: “Not enough storage” error occurs when you open Property Pages in the Japanese versions of Visual Studio.
Workaround: None.

Title: After upgrading to Windows Vista upgrade, the New Project dialog names for Windows Mobile 5.0 nodes are changed for managed projects.

Description: After upgrading to Windows Vista the project nodes for Windows Mobile 5.0 may have their names changed. No functionality is lost but the names are not clear. For example, the names “Windows Mobile 5.0 Pocket PC” and “Windows Mobile 5.0 Smartphone” are changed to “PPC” and “SP” respectively.
Workaround: No functionality has been lost, just select respective name for the new projects.

Title: Visual Studio fails to create native C++ projects

Description: When a developer tries to create a native C++ Smart Devices application Visual Studio repeatedly displays the 'New Project' dialog and can't proceed forward.
Workaround: This workaround requires editing the registry. This process can cause considerable harm to a machine and it is recommended that you perform a full backup prior to this action. To solve the problem, run RegEdit and located the registry key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Ext\PreApproved”. Right click on the key and add a new key. Use “{D245F352-3F45-4516-B1E6-04608DA126CC}" as the key name.

Title: Using Remote Tools on Windows Vista

Description: Even if you run Visual Studio with elevated administrator permissions, the Remote Tools will run as normal user, unless you explicitly run them elevated. For example, if Visual Studio is running with elevated administrator permissions and you Connect to Device, start a Remote Tool (e.g., File Explorer), and then select the same device, a message will appear that says, "Error: The current VMID is in use. Wait for the other application to exit."
Workaround: Start the Remote Tools using elevated administrator permissions.

Debugging

Title: Cannot Cradle the Emulator in Windows Vista

Description: In Windows Vista, ActiveSync-over-DMA fails and thus the emulator cannot be cradled
Workaround: None

Title: Device Emulator Manager (DEM) UI Corrupted when aborting the emulator

Description: DEM UI becomes corrupted after multiple connections and aborts.
Workaround: Exit DEM and re-launch it to refresh the UI.

Deployment
Title: SQL Server Mobile Edition databases created on Windows XP or older operating systems (and device emulators) do not work on Windows Vista and vice versa.

Description: Databases created on Windows XP or on Smart Devices cannot be read on Windows Vista.
Similarly SQL Mobile Edition databases created on Windows Vista cannot be read/written to a Device or Windows XP.
Workaround: When working on Windows Vista you will need to make a copy of the existing database to enable you to build an application that uses it. If you plan to use the database on a device or in the Windows Mobile emulator you will need to use a database created on Windows XP

Jopp kör Vista 64 bit

Tog livet av en session som ej ville sluta via Aktivitetshanteraren
Då kom det upp en ruta att Windows söker efter en lösning på problemet.
Och hör och häpna, Windows hittade själv problemet och nu funkar det igen.

En stund, sedan är det likadant igen.
Denna gång gick det inte att få windows att laga problemet

Funderar på om det kan vara något med branväggar eller andra spärrar
Kör McAfee
Eller någon inställning i VS2005???

Kör lite egna javascript samt AJAX på sidan.


Blev dock inte så klok på ditt tipps Pelle.


mvh Roland

Var nog för bra för att vara sant, att det lagar sig självt.
Bara slumpen att det funkade ett par gånger.

Testat med ett minimalt projekt med endast asp.net utan AJAX och egna javascript.
Alltså en form med bara en knapp på.

Samma sak. Webbläsaren hänger sig och vägrar avsluta utan att jag tvingar det via "Stop Debugging"

Har funkat bra tidigare men återstår väll bara ominstallation.

mvh Roland