BUG: AppDomainUnloadedException is thrown when you call a virtual destructor on a __nogc class during an AppDomain unload (837317)

MORE INFORMATION

Steps to reproduce the behavior

1. Start Visual Studio .NET 2003.
2. On the File menu, point to New, and then click Project.
3. Under Project Types, click Visual C++ Projects, and then click Class Library (.NET) under Templates.
4. In the Name box, type Server, and then click OK.
5. In Solution Explorer, expand Header Files under Server.
6. Double-click Server.h under Header Files.
7. In the Code window, replace the code in the Server namespace with the following code:

   //workaround 3: Use the #pragma directive by uncommenting the following line.
   //#pragma unmanaged	
   	//workaround 1: Make __nogc as __gc in the following line 
   	__nogc class CauseAppDomainUnloadedException
   	{
   	public:
   		//workaround 2: Remove the virtual keyword
   		virtual ~CauseAppDomainUnloadedException()
   		{
   		}
   	};
   
   //workaround 3: Use the #pragma directive by uncommenting the following line.
   //#pragma managed
   	public __gc class ManagedClass : public System::MarshalByRefObject
   	{
   public:
   		ManagedClass()
   		{
   			//workaround 1: Make __nogc as __gc in the following line
   			m_pInternal = __nogc new CauseAppDomainUnloadedException();
   		}
   		~ManagedClass()
   		{
   			// The destructor is called when ~ManagedClass is called by
   			// the GC when the AppDomain is being unloaded.
   			// If ~CauseAppDomainUnloadedException() is virtual
   			// then an AppDomainUnloadedException occurs in the delete
   			// statement. If ~CauseAppDomainUnloadedException() is
   			// NOT virtual, then it does not occur.			 
   			delete m_pInternal; 
   			m_pInternal = 0;			
   			
   		}
           
   
   	private:
   		//workaround 1: Make __nogc as __gc in the following line
   		CauseAppDomainUnloadedException __nogc* m_pInternal;
   	};

8. In Solution Explorer, double-click Stdafx.h under Header Files.
9. Add the following code in the Code window:

   #include <windows.h>
   #include <vcclr.h>

10. In Solution Explorer, right-click the Server project node, and then click Properties.
11. In the Server Property Pages dialog box, expand Linker under Configuration Properties, and then click Input.
12. Type msvcrt.lib in the Additional Dependencies box, and the click OK.
13. Press CTRL+SHIFT+S to save the project, and then press CTRL+SHIFT+B to build the solution.
    
    This builds the solution, and the Server.dll file is created in the Debug folder of the project.
14. In Solution Explorer, right-click the solution node, point to Add, and then click New Project.
15. Under Project Types click Visual C# Projects, and then click Console Application under Templates.
16. In the Name box, type Client, and then click OK.
17. In Solution Explorer, right-click the Client project node, and then click Add Reference.
18. In the Add Reference dialog box, click Browse, and then select the Server.dll file that you created in Step 14.
19. Click OK to add the reference.
20. In Solution Explorer, double-click Class1.cs under the Client project folder.
21. Add the following code to the top of the Code window after the using statement:

    using System.Reflection;
    using System.Runtime.InteropServices;

22. Replace the code in the Main function with the following code:

    AppDomain domain = AppDomain.CreateDomain("A new domain");
    //domain.InitializeLifetimeService();
    
    Server.ManagedClass mc = (Server.ManagedClass) domain.CreateInstanceAndUnwrap(
    	typeof(Server.ManagedClass).Assembly.FullName, 
    	typeof(Server.ManagedClass).FullName,
    	false, BindingFlags.Default,null,null,null,null,null);
    
    //ServerCSharp.ManagedClass mc = new ServerCSharp.ManagedClass();
    
    AppDomain.Unload(domain);

23. In Solution Explorer, right-click the Client project node, and then click Set as StartUp Project.
24. Press CTRL+SHIFT+S to save the project, and then press CTRL+SHIFT+B to build the solution.
25. Press F5 to run the application in Debug mode.
    
    You notice the exception in the Console window.