I am already fairly certain that what I am trying to do based on the
contstraints I have can't be done.
However hoping someone can prove me wrong.

I need to write an assembly that I can call from .net 1.1, .net 2.0,
classic asp, and possibly vb6.
The constraints are no web services. I would like to develop the
solution in .net 2.0 as opposed to 1.1.
The last constraint is no the projects and webs written in .net 1.1
can't be upgraded at this time.

I tried exposing my objects from my 2.0 assembly as com. Solves the
problem perfectly for classic asp and vb.6 and .net 2.0. 1.1 is the
difficult one. I tried to connect to my com object using both early
and late binding and as I expected it would not work.
If anyone has gotten this to work, please do let me know.
Thanks in advance
sincerely
Ralph

You cant have 2 versions of the framework loaded to the same process. You
would need to configure it as a 'Server Application' in the COM configuration
so it ran in its own process. Give it a try and let me know.

--
Ciaran O''Donnell
http://wannabedeveloper.spaces.live.com


"Ralph" wrote:

> I am already fairly certain that what I am trying to do based on the
> contstraints I have can't be done.
> However hoping someone can prove me wrong.
>
> I need to write an assembly that I can call from .net 1.1, .net 2.0,
> classic asp, and possibly vb6.
> The constraints are no web services. I would like to develop the
> solution in .net 2.0 as opposed to 1.1.
> The last constraint is no the projects and webs written in .net 1.1
> can't be upgraded at this time.
>
> I tried exposing my objects from my 2.0 assembly as com. Solves the
> problem perfectly for classic asp and vb.6 and .net 2.0. 1.1 is the
> difficult one. I tried to connect to my com object using both early
> and late binding and as I expected it would not work.
> If anyone has gotten this to work, please do let me know.
> Thanks in advance
> sincerely
> Ralph
>
>

Thanks Ciaran,
I completely forgot to try that.
After quite some tweaking I did get that to work.
Late binding from the 1.1 consumer worked only.
VS 2003 still wouldn't let me create a reference to the dcom.



On Oct 7, 10:55*am, Ciaran O''Donnell
<CiaranODonn...@discussions.microsoft.com> wrote:
> You cant have 2 versions of the framework loaded to the same process. You
> would need to configure it as a 'Server Application' in the COM configuration
> so it ran in its own process. Give it a try and let me know.
>
> --
> Ciaran O''Donnellhttp://wannabedeveloper.spaces.live.com
>
>
>
> "Ralph" wrote:
> > I am already fairly certain that what I am trying to do based on the
> > contstraints I have can't be done.
> > However hoping someone can prove me wrong.
>
> > I need to write an assembly that I can call from .net 1.1, .net 2.0,
> > classic asp, and possibly vb6.
> > The constraints are no web services. *I would like to develop the
> > solution in .net 2.0 as opposed to 1.1.
> > The last constraint is no the projects and webs written in .net 1.1
> > can't be upgraded at this time.
>
> > I tried exposing my objects from my 2.0 assembly as com. *Solves the
> > problem perfectly for classic asp and vb.6 and .net 2.0. *1.1 is the
> > difficult one. *I tried to connect to my com object using both early
> > and late binding and as I expected it would not work.
> > If anyone has gotten this to work, please do let me know.
> > Thanks in advance
> > sincerely
> > Ralph- Hide quoted text -
>
> - Show quoted text -