Sadly there is very little documentation on the interop toolkit the way I am using it. Ironically the answer was in the order of doing things. If I execute the setparent function before I open the vb .net form it works perfectly. Lots of time lost for a stupid problem.
Such a Larry
Thanks but that did not help the vb6 form is still frozen. As soon as I get this working I can begin the conversion.
Such a Larry
These are really good people. I like them and don't mind being responsible for converting the code. I have made some progress on this issue. The setparent now seems to be working. The vb6 form is now appearing in the .net container. The problem was passing the parent from vb6 and that is now handled. So setparent works now but it's followed by a send message, setforegroundwindow and lockwindowupdate which appear not to be working. My declarations are as follows: _ Private Shared Function SetParent(ByVal hWndChild As IntPtr, ByVal hWndNewParent As IntPtr) As Int32 End Function Public Declare Auto Function SendMessage Lib "user32.dll" ( _ ByVal hWnd As IntPtr, _ ByVal wMsg As Int32, _ ByVal wParam As Int32, _ ByVal s As String _ ) As Int32 _ Private Shared Function SetForegroundWindow(ByVal hwnd As IntPtr) As IntPtr End Function _ Private Shared Function LockWindowUpdate(ByVal hwndLock As IntPtr) As Boolean End Function and the code is: SetParent(mintFormHandle, Me.Handle.ToInt32) SendMessage(mintFormHandle, WM_ACTIVATE, 1, IntPtr.Zero) SetForegroundWindow(mintFormHandle) LockWindowUpdate(0) Me.Refresh() Any suggestions?
Such a Larry
Yes of course the best thing would be to convert the code but its not going to happen right away when there is so much code and so many customers and users (100's). By stripping the vb6 forms borders and putting them in a .net wrapper we get a really nice look in Windows 7 & 8 and now we have more time to properly analyze and convert the remaining code and marketing can demo an upgraded look and feel to the application. As far as sit there. The vb6 form is frozen but you can drag stuff over it without a paint problem. I wish I could upload the code. Larry
Such a Larry
Hi, I posted this in general questions and then realized I should have posted it here. I have a large vb6 app that I turned into a dll so I could run it from vb .net. When I run the vb6 & .net projects in debug everything works fine. If I open the forms non modally everything works fine all the time. However when I compile the vb6 into a dll the vb6 forms are not being placed in the .Net container form when I open them modally (non modal is OK). The vb6 form just sits in the upper left of the screen. I came up with this solution based on an article by Eduardo Campano on embedding vb6 forms in .Net applications from July 2007. Great article and a good idea if you have a million lines of code to convert to .net. I have sample code but don't see how to upload it to the forum. The code for loading the vb6 into the container is from the container load event in .net: SetParent(mintFormHandle, Me.Handle.ToInt32) SendMessage(Me.Handle.ToInt32, WM_NCACTIVATE, 1, 0) SetForegroundWindow(Me.Handle.ToInt32) LockWindowUpdate(0)
Such a Larry
I hope that you will publish an article on what you end up doing. There is so little documentation on doing anything with sound including direct sound libraries other than playing wav files. I would love to see an examples of getting to the sound card buffer with either managed or unmanaged code. I don't believe there is an article of any kind on the subject. Larry Freedman
Such a Larry
I have a simple problem and find it hard to believe there isn't an article or documentation around on how to solve it. Probably just looking in the wrong place. Anyway I have a form with a grid bound to a table in the dataset. There are several other tables in the dataset which provide detail info for the parent record. My main form has a grid and a tab control. When the user selects a tab a control bound to the original form is added with the detail info from the appropriate table. No problem so far. I just pass the dataset and filter in the new routine of the control. Now when I change recors in the master grid I would like the detail in the loaded control to be synchronized. Anyone have a simple example of this or know an easy to understand article on maintaining concurrency between a form and a loaded control?
Such a Larry