.NET Framework - Problem in closing MDIChild Form having ActiveX control

I have VB2005 Application. It has VB MDI Form and MDI Child form.
The child Form hosts an ActiveX control.
when I close the ChildForm at runtime, It gives error message
This problem occurs only the activex controls is hosted in MDI Child form.

I hosted the activex control in a Windows Form. It works fine on close.
The problem I see only with MDI child form.
I think, the activex control is not disposed properly in case of MDI child
form.
Could anyone help me in solving this.

  RobinS replied...

Are you disposing of the ActiveX control in the Form_Closing event of your
MDI child? Or you could also try disposing your MDI child and see if that
helps.

Robin S.
---------------------------------------------------

NET Framework Relationship between Application.Exit() and AppDomain Hi, Does Application.Exit() apply only to the AppDomain in which it is called? Is it the same as in WPF – a single Application object per AppDomain? Generally speaking, what is the relationship between an Application object and AppDomain objects? Regards, Sunny S. One AppDomain per application. One or more AppDomains in a Process. WPF doesn't change this as WPF is still a .NET application and is still run by the CLR. Application.Exit will kill the application you are calling it on and therefore the AppDomain it is running in. As far

NET Framework Another option for keeping application tiers independent The Unavoidable Dependency between the User Interface and the Data Tier There is a big push by software engineers, consultants and authors alike that a clean separation of application logic into tiers is the only way to write code. However, in the real world comes from. However, in reality, this is rarely the whole truth. In an N-tier application (specifically a three-tier application), there are definite benefits of keeping the user interface unaware of where its data is user interface passing connection information. But, if we are requiring users to log into our application, the interface has to know a little about the data source anyway. Your shop may 92s awareness to a minimum. The trick is that the user interface changes for each application. You want to reuse your domain logic and data objects as much as possible. However user interface. The idea is to create a new class that is specific to the application. Its sole purpose in existence is to grab data from the data tier and pass about it, you may wonder whether this new mediator makes the domain dependent on the application. It is easy to see that the data tier is like a service, data is

NET Framework Autodeployed Win App - Vista IIS 7.0 I have created a three tier application consisting of Client (Exe and Exe.Config), Middle (WebServices) and Database tiers. The Client tier Config file which contains a ConnectionString pointing to the Database. I have auto-deployed this application (the Client and Middle tiers) on a Windows 2000 server with IIS 5. From my Windows XP machine (with IIS 5) I can run this application just fine using a URL such as: http: / / myServer / myApps / myApp.Exe. Also, it connects XP machine (with IIS 5) to Vista with IIS 7.0. When I run the application on this machine, using the same URL as above, it attempts to connect to the server. Do I have to make any changes in IIS 7.0 to allow the application to read and download Exe.Config files that are not local? Any suggestions? Thanks in advance. I should add that the three tier Windows application was developed using Visual Studio 2003 on .NET Framework 1.1 SP 1. Hi NormD your description and did see the problem on my side. When I place my test application(with a exe.config) on IIS 5, and then launch the application with a URL, such as: http: / / localhost / TestApp / TestApp.exe the application could access the

Passing URI Parameters to WPF App Affecting Deployment I have created a WPF "stand-alone" application that is deployed via ClickOnce over http. One of the features I want to take this? Thanks for the assistance. Hi, Based on my understanding, you have a WPF Windows Application project and publish the application via ClickOnce. Your problem is that after you install the WPF application on a client machine and active the WPF application via a URL with changed parameters, you get a prompt indicating that the application was deployed from a different location. If I'm off base, please feel free to the problem. The following are the steps of my test: 1. Create a WPF Windows Application project and add a TextBox on the Window1.xaml. In the Window1.xaml.cs file Publish Options dialog, select the checkbox before the 'Allow URL parameters to be passed to application' option. 5. Publish the application and install it on the local machine. 6. Open IE

NET Framework [VB 2008] Warum dispose aller Fenster bei exit Application.run? Hi, ich bin heute auf ein Verhalten gestossen, das ich f?r nicht so Form With {.Text = "f2"} f1.Show() f2.Show() fMain = New Form With {.Text = "fMain #1"} Application.Run(fMain) End Sub End Class Festgestellt habe ich, dass _in_ Application.Run, nachdem fMain geschlossen wurde, die Dispose-Methode _aller_ ge?ffneten Fenster aufgerufen wird. Ich finde das nicht richtig. Deutlich wird das, wenn man nach dem Application.Run diese Zeilen einf?gt: fMain = New Form With {.Text = "fMain #2"} Application.Run(fMain) Schlie?t man nun die erste Instanz von fMain werden f1 und f2 Dispose(Boolean) System.dll!System.ComponentModel.Component.Dispose() System.Windows.Forms.dll!System.Windows.Forms.Application.ThreadWindows.Dispose() System.Windows.Forms.dll!System.Windows.Forms.Application.ThreadContext.DisposeThreadWindows() System.Windows.Forms.dll!System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(int, int, int) System.Windows.Forms.dll!System