|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Remoting between 2.0 and 1.1Hi everybody,
I have a 3rd party 1.1 framework dll that I want to use in a .net 2.0 application. Alvin Bruney already told me here that I can't use it as a reference in my 2.0 app because it will be run in 2.0. So, I'm wondering if it's possible to make a little 1.1 app that will reference that dll and then it will communicate with my 2.0 app using remoting. Will that work? Hugo Vale wrote:
> Hi everybody, I don't think so. My experience so far is that SERIALIZATION has > > I have a 3rd party 1.1 framework dll that I want to use in a .net 2.0 > application. Alvin Bruney already told me here that I can't use it as a > reference in my 2.0 app because it will be run in 2.0. So, I'm wondering if > it's possible to make a little 1.1 app that will reference that dll and then > it will communicate with my 2.0 app using remoting. Will that work? > changed, and as such prevents remoting between 1.1 and 2.0. I have called 1.1 components from 2.0. It worked for me in a limited use. Even if it did not for you, then how about providing a COM wrapper on your 3rd party, and calling that from your 2.0 code, as an isolation layer. I know it is perverse, and will probably be doggy, but maybe it will help get you through a tough spot temporarily. Thanks for the info Gillie,
At this point I'm ready to try anything. The only thing is, that I don't even know where to start with that COM wrapper, do you know any good articles on the web where I can look at? Thanks in advance Show quote "Lee Gillie" <Lee@nospam.odp.com> wrote in message news:uV4dvXdAGHA.3180@TK2MSFTNGP10.phx.gbl... > Hugo Vale wrote: >> Hi everybody, >> >> I have a 3rd party 1.1 framework dll that I want to use in a .net 2.0 >> application. Alvin Bruney already told me here that I can't use it as a >> reference in my 2.0 app because it will be run in 2.0. So, I'm wondering >> if it's possible to make a little 1.1 app that will reference that dll >> and then it will communicate with my 2.0 app using remoting. Will that >> work? >> > > I don't think so. My experience so far is that SERIALIZATION has changed, > and as such prevents remoting between 1.1 and 2.0. > > I have called 1.1 components from 2.0. It worked for me in a limited use. > Even if it did not for you, then how about providing a COM wrapper on your > 3rd party, and calling that from your 2.0 code, as an isolation layer. I > know it is perverse, and will probably be doggy, but maybe it will help > get you through a tough spot temporarily. Believe it or not the documentation has some great information.
Also, to learn, make a new project, choose class library as the type. ADD NEW ITEM to the class. Choose "COM CLASS". You will notice there are simply a few project settings made, and a little extra code added to the class. HTH - Lee Hugo Vale wrote: Show quote > Thanks for the info Gillie, > > At this point I'm ready to try anything. The only thing is, that I don't > even know where to start with that COM wrapper, do you know any good > articles on the web where I can look at? > > Thanks in advance > > "Lee Gillie" <Lee@nospam.odp.com> wrote in message > news:uV4dvXdAGHA.3180@TK2MSFTNGP10.phx.gbl... > >>Hugo Vale wrote: >> >>>Hi everybody, >>> >>>I have a 3rd party 1.1 framework dll that I want to use in a .net 2.0 >>>application. Alvin Bruney already told me here that I can't use it as a >>>reference in my 2.0 app because it will be run in 2.0. So, I'm wondering >>>if it's possible to make a little 1.1 app that will reference that dll >>>and then it will communicate with my 2.0 app using remoting. Will that >>>work? >>> >> >>I don't think so. My experience so far is that SERIALIZATION has changed, >>and as such prevents remoting between 1.1 and 2.0. >> >>I have called 1.1 components from 2.0. It worked for me in a limited use. >>Even if it did not for you, then how about providing a COM wrapper on your >>3rd party, and calling that from your 2.0 code, as an isolation layer. I >>know it is perverse, and will probably be doggy, but maybe it will help >>get you through a tough spot temporarily. > > > Hi Lee,
I've tried doing a COM class to wrap that 3rd party dll. It all went fine until I referenced it on my 2.0 project. When I do that, it tells me that it is a .net com class and I must use the dll directly instead of the COM wrapper, if I do that it treats it like a regular .net dll and running it in 2.0 I've tried not referencing it and use the CreateObject("MyWrapper.ComWrapper") but it still treats it as being .net. Is there a way of avoiding this and treat it as regular COM? Hugo Vale www.datastreamcs.com Show quote "Lee Gillie" <Lee@nospam.odp.com> wrote in message news:O1IYp1lAGHA.3064@TK2MSFTNGP10.phx.gbl... > Believe it or not the documentation has some great information. > > Also, to learn, make a new project, choose class library as the type. ADD > NEW ITEM to the class. Choose "COM CLASS". You will notice there are > simply a few project settings made, and a little extra code added to the > class. > > HTH - Lee > > Hugo Vale wrote: >> Thanks for the info Gillie, >> >> At this point I'm ready to try anything. The only thing is, that I don't >> even know where to start with that COM wrapper, do you know any good >> articles on the web where I can look at? >> >> Thanks in advance >> >> "Lee Gillie" <Lee@nospam.odp.com> wrote in message >> news:uV4dvXdAGHA.3180@TK2MSFTNGP10.phx.gbl... >> >>>Hugo Vale wrote: >>> >>>>Hi everybody, >>>> >>>>I have a 3rd party 1.1 framework dll that I want to use in a .net 2.0 >>>>application. Alvin Bruney already told me here that I can't use it as a >>>>reference in my 2.0 app because it will be run in 2.0. So, I'm wondering >>>>if it's possible to make a little 1.1 app that will reference that dll >>>>and then it will communicate with my 2.0 app using remoting. Will that >>>>work? >>>> >>> >>>I don't think so. My experience so far is that SERIALIZATION has changed, >>>and as such prevents remoting between 1.1 and 2.0. >>> >>>I have called 1.1 components from 2.0. It worked for me in a limited use. >>>Even if it did not for you, then how about providing a COM wrapper on >>>your 3rd party, and calling that from your 2.0 code, as an isolation >>>layer. I know it is perverse, and will probably be doggy, but maybe it >>>will help get you through a tough spot temporarily. >> >>  |
|||||||||||||||||||||||
Other interesting topics