Re: Putting COM interop type in the container
Sorry for the late answer The compilation errors were type not found, it didn't find a lot of COM types. I didn't find any reason for these compilation errors I spent a few hours checking the correct COM component was registered, tried to directly reference the Interop.xx.dll, cleared the project output etc. but no way nothing worked. I had to check Embed Interop Type to make it compile again. Very strange. I fixed my original problem using a simple wrapper around the COM component with a unique property exposing the COM component, and registering/resolving this wrapper. So when accessing the property the c# type equivalence is used. Of course it's just a work around, but as it's the only COM component I register it's enough. It would not be the case if I had dozen of COM component :-) Indeed it would be nice to include this in windsor, but depending on how often users need it I do not know if it's worth it... 2015-03-17 0:38 GMT+01:00 hammett hamm...@gmail.com: Yep. Thanks Ian. On Tue, Mar 17, 2015 at 12:11 PM, IanYates i...@medicalit.com.au wrote: https://msdn.microsoft.com/en-us/library/dd997297(VS.100).aspx for those who are interested... (I don't have need for this feature at the moment but it's good to know for the future or if anyone else is keen on a PR) On Monday, March 16, 2015 at 11:42:28 AM UTC+10, hammett wrote: NoPia introduces a new way of type equivalence. I'd think Windsor will need a little change support the other kind of type equivalence. PR is welcome. On Sun, Mar 15, 2015 at 11:00 PM, Fabrice faze...@gmail.com wrote: Hi I've some problème with COM interop type put in the container, I can't resolve. I think I understand why, but don't see any solution so maybe someone can help I've 2 projects (P1 P2) which both reference a COM library (Redemption) with Embed Interop Type = true. I've tried to set this to false but then I've a lot of compilation errors. P1 have the RDOSession object, and put it in the container. P2 try to resolve the RDOSession object, and if fail. I suppose the reason is that P1 and P2 have their own RDOSession type embeded in the DLL. But .NET 4 is able to manage that, if I directly use the RDOSession given by P1 I've no problem. It seems that the container can't manage that and see both version of RDOSession as different type (which, in fact, it is) and trying to resolve P2.RDOSession doesn't return P1.RDOSession. Does someone see any solution to this ? -- You received this message because you are subscribed to the Google Groups Castle Project Users group. To unsubscribe from this group and stop receiving emails from it, send an email to castle-project-users+unsubscr...@googlegroups.com. To post to this group, send email to castle-pro...@googlegroups.com. Visit this group at http://groups.google.com/group/castle-project-users. For more options, visit https://groups.google.com/d/optout. -- Cheers, hammett http://www.d-collab.com/ http://www.hammettblog.com/ -- You received this message because you are subscribed to the Google Groups Castle Project Users group. To unsubscribe from this group and stop receiving emails from it, send an email to castle-project-users+unsubscr...@googlegroups.com. To post to this group, send email to castle-project-users@googlegroups.com. Visit this group at http://groups.google.com/group/castle-project-users. For more options, visit https://groups.google.com/d/optout. -- Cheers, hammett http://www.d-collab.com/ http://www.hammettblog.com/ -- You received this message because you are subscribed to the Google Groups Castle Project Users group. To unsubscribe from this group and stop receiving emails from it, send an email to castle-project-users+unsubscr...@googlegroups.com. To post to this group, send email to castle-project-users@googlegroups.com . Visit this group at http://groups.google.com/group/castle-project-users. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Castle Project Users group. To unsubscribe from this group and stop receiving emails from it, send an email to castle-project-users+unsubscr...@googlegroups.com. To post to this group, send email to castle-project-users@googlegroups.com. Visit this group at http://groups.google.com/group/castle-project-users. For more options, visit https://groups.google.com/d/optout.
Re: Putting COM interop type in the container
Yep. Thanks Ian. On Tue, Mar 17, 2015 at 12:11 PM, IanYates i...@medicalit.com.au wrote: https://msdn.microsoft.com/en-us/library/dd997297(VS.100).aspx for those who are interested... (I don't have need for this feature at the moment but it's good to know for the future or if anyone else is keen on a PR) On Monday, March 16, 2015 at 11:42:28 AM UTC+10, hammett wrote: NoPia introduces a new way of type equivalence. I'd think Windsor will need a little change support the other kind of type equivalence. PR is welcome. On Sun, Mar 15, 2015 at 11:00 PM, Fabrice faze...@gmail.com wrote: Hi I've some problème with COM interop type put in the container, I can't resolve. I think I understand why, but don't see any solution so maybe someone can help I've 2 projects (P1 P2) which both reference a COM library (Redemption) with Embed Interop Type = true. I've tried to set this to false but then I've a lot of compilation errors. P1 have the RDOSession object, and put it in the container. P2 try to resolve the RDOSession object, and if fail. I suppose the reason is that P1 and P2 have their own RDOSession type embeded in the DLL. But .NET 4 is able to manage that, if I directly use the RDOSession given by P1 I've no problem. It seems that the container can't manage that and see both version of RDOSession as different type (which, in fact, it is) and trying to resolve P2.RDOSession doesn't return P1.RDOSession. Does someone see any solution to this ? -- You received this message because you are subscribed to the Google Groups Castle Project Users group. To unsubscribe from this group and stop receiving emails from it, send an email to castle-project-users+unsubscr...@googlegroups.com. To post to this group, send email to castle-pro...@googlegroups.com. Visit this group at http://groups.google.com/group/castle-project-users. For more options, visit https://groups.google.com/d/optout. -- Cheers, hammett http://www.d-collab.com/ http://www.hammettblog.com/ -- You received this message because you are subscribed to the Google Groups Castle Project Users group. To unsubscribe from this group and stop receiving emails from it, send an email to castle-project-users+unsubscr...@googlegroups.com. To post to this group, send email to castle-project-users@googlegroups.com. Visit this group at http://groups.google.com/group/castle-project-users. For more options, visit https://groups.google.com/d/optout. -- Cheers, hammett http://www.d-collab.com/ http://www.hammettblog.com/ -- You received this message because you are subscribed to the Google Groups Castle Project Users group. To unsubscribe from this group and stop receiving emails from it, send an email to castle-project-users+unsubscr...@googlegroups.com. To post to this group, send email to castle-project-users@googlegroups.com. Visit this group at http://groups.google.com/group/castle-project-users. For more options, visit https://groups.google.com/d/optout.
Re: Putting COM interop type in the container
https://msdn.microsoft.com/en-us/library/dd997297(VS.100).aspx for those who are interested... (I don't have need for this feature at the moment but it's good to know for the future or if anyone else is keen on a PR) On Monday, March 16, 2015 at 11:42:28 AM UTC+10, hammett wrote: NoPia introduces a new way of type equivalence. I'd think Windsor will need a little change support the other kind of type equivalence. PR is welcome. On Sun, Mar 15, 2015 at 11:00 PM, Fabrice faze...@gmail.com javascript: wrote: Hi I've some problème with COM interop type put in the container, I can't resolve. I think I understand why, but don't see any solution so maybe someone can help I've 2 projects (P1 P2) which both reference a COM library (Redemption) with Embed Interop Type = true. I've tried to set this to false but then I've a lot of compilation errors. P1 have the RDOSession object, and put it in the container. P2 try to resolve the RDOSession object, and if fail. I suppose the reason is that P1 and P2 have their own RDOSession type embeded in the DLL. But .NET 4 is able to manage that, if I directly use the RDOSession given by P1 I've no problem. It seems that the container can't manage that and see both version of RDOSession as different type (which, in fact, it is) and trying to resolve P2.RDOSession doesn't return P1.RDOSession. Does someone see any solution to this ? -- You received this message because you are subscribed to the Google Groups Castle Project Users group. To unsubscribe from this group and stop receiving emails from it, send an email to castle-project-users+unsubscr...@googlegroups.com javascript:. To post to this group, send email to castle-pro...@googlegroups.com javascript:. Visit this group at http://groups.google.com/group/castle-project-users. For more options, visit https://groups.google.com/d/optout. -- Cheers, hammett http://www.d-collab.com/ http://www.hammettblog.com/ -- You received this message because you are subscribed to the Google Groups Castle Project Users group. To unsubscribe from this group and stop receiving emails from it, send an email to castle-project-users+unsubscr...@googlegroups.com. To post to this group, send email to castle-project-users@googlegroups.com. Visit this group at http://groups.google.com/group/castle-project-users. For more options, visit https://groups.google.com/d/optout.
Putting COM interop type in the container
Hi I've some problème with COM interop type put in the container, I can't resolve. I think I understand why, but don't see any solution so maybe someone can help I've 2 projects (P1 P2) which both reference a COM library (Redemption) with Embed Interop Type = true. I've tried to set this to false but then I've a lot of compilation errors. P1 have the RDOSession object, and put it in the container. P2 try to resolve the RDOSession object, and if fail. I suppose the reason is that P1 and P2 have their own RDOSession type embeded in the DLL. But .NET 4 is able to manage that, if I directly use the RDOSession given by P1 I've no problem. It seems that the container can't manage that and see both version of RDOSession as different type (which, in fact, it is) and trying to resolve P2.RDOSession doesn't return P1.RDOSession. Does someone see any solution to this ? -- You received this message because you are subscribed to the Google Groups Castle Project Users group. To unsubscribe from this group and stop receiving emails from it, send an email to castle-project-users+unsubscr...@googlegroups.com. To post to this group, send email to castle-project-users@googlegroups.com. Visit this group at http://groups.google.com/group/castle-project-users. For more options, visit https://groups.google.com/d/optout.
Re: Putting COM interop type in the container
What sort of compilation errors do you get when the COM types aren't embedded? Maybe we can start there to fix it? On Sunday, March 15, 2015 at 8:00:47 PM UTC+10, Fabrice wrote: Hi I've some problème with COM interop type put in the container, I can't resolve. I think I understand why, but don't see any solution so maybe someone can help I've 2 projects (P1 P2) which both reference a COM library (Redemption) with Embed Interop Type = true. I've tried to set this to false but then I've a lot of compilation errors. P1 have the RDOSession object, and put it in the container. P2 try to resolve the RDOSession object, and if fail. I suppose the reason is that P1 and P2 have their own RDOSession type embeded in the DLL. But .NET 4 is able to manage that, if I directly use the RDOSession given by P1 I've no problem. It seems that the container can't manage that and see both version of RDOSession as different type (which, in fact, it is) and trying to resolve P2.RDOSession doesn't return P1.RDOSession. Does someone see any solution to this ? -- You received this message because you are subscribed to the Google Groups Castle Project Users group. To unsubscribe from this group and stop receiving emails from it, send an email to castle-project-users+unsubscr...@googlegroups.com. To post to this group, send email to castle-project-users@googlegroups.com. Visit this group at http://groups.google.com/group/castle-project-users. For more options, visit https://groups.google.com/d/optout.
Re: Putting COM interop type in the container
NoPia introduces a new way of type equivalence. I'd think Windsor will need a little change support the other kind of type equivalence. PR is welcome. On Sun, Mar 15, 2015 at 11:00 PM, Fabrice faze1...@gmail.com wrote: Hi I've some problème with COM interop type put in the container, I can't resolve. I think I understand why, but don't see any solution so maybe someone can help I've 2 projects (P1 P2) which both reference a COM library (Redemption) with Embed Interop Type = true. I've tried to set this to false but then I've a lot of compilation errors. P1 have the RDOSession object, and put it in the container. P2 try to resolve the RDOSession object, and if fail. I suppose the reason is that P1 and P2 have their own RDOSession type embeded in the DLL. But .NET 4 is able to manage that, if I directly use the RDOSession given by P1 I've no problem. It seems that the container can't manage that and see both version of RDOSession as different type (which, in fact, it is) and trying to resolve P2.RDOSession doesn't return P1.RDOSession. Does someone see any solution to this ? -- You received this message because you are subscribed to the Google Groups Castle Project Users group. To unsubscribe from this group and stop receiving emails from it, send an email to castle-project-users+unsubscr...@googlegroups.com. To post to this group, send email to castle-project-users@googlegroups.com. Visit this group at http://groups.google.com/group/castle-project-users. For more options, visit https://groups.google.com/d/optout. -- Cheers, hammett http://www.d-collab.com/ http://www.hammettblog.com/ -- You received this message because you are subscribed to the Google Groups Castle Project Users group. To unsubscribe from this group and stop receiving emails from it, send an email to castle-project-users+unsubscr...@googlegroups.com. To post to this group, send email to castle-project-users@googlegroups.com. Visit this group at http://groups.google.com/group/castle-project-users. For more options, visit https://groups.google.com/d/optout.
