Click here to Skip to main content
15,885,128 members

Comments by ARopo (Top 60 by date)

ARopo 5-Oct-15 6:32am View    
I never did get to the bottom of this, ended up loading the class library dynamically and using reflection to call it. I think in may be something to do with dll initialization and the timing and order of things.
ARopo 23-Jul-12 11:35am View    
what is it you are trying to access from vb6? the solution in this post is for hosting a .net user control on a vb6 form.

Sounds like either your manifest is not embedded or is not correct - use mt.exe to extract and check the manifest from your .net dll. Also try using sxstrace to diagnose the problem. You also need a manifest for the VB6 exe that refers to the .net dlls as dependencies.
ARopo 10-May-12 6:36am View    
Solution 3 could indeed be the case, there are many reasons why debug and release can give different outcomes, I've certainly been tripped up by putting vital code into an assert macro.
ARopo 19-Dec-11 5:54am View    
Can't see any reason for this in the code provied , where is m the error refers to parameter m
ARopo 12-Sep-11 9:09am View    
Thanks, I did have binary compatability on, but still got new guids. However your answer led me to look at it in more detail and I discovered that the binary compatable dll referrenced had a different type lib version to the dll I was buildinf and hense generated new guids. I updated the dll reference and hey presto consistant guids.