1.1 Famework needed for an applications API

15 Jun 2006 12:28 AM

ngpost1

I am wanting to write an application and/or a Web service that will
connect to another commercial application via that comercial
application's API. I would like to write my application using VS.Net
2005 (as opposed to 2003). The commercial application can only run
with the 1.1 Framework. Is there anyway to have my application utilize
the 2.0 Framework but have the other application utilize the 1.1
Framework when it is instantiated via it's API? Putting
app_name.exe.config files in the application's folder works fine when
launching that app via it's EXE but it seems that the API doesn't
read those files.

Thanks!!!

16 Jun 2006 7:51 AM

Dmytro Lapshyn [MVP]

Hi,

Can you please elaborate on the nature of the API you are using? Is it just
a managed code assembly? If so, craft an app.config file for your OWN
application in a way to redirect all binding requests for 1.1 assemblies to
their 2.0 counterparts. Then, when you will be loading the API dll to the
app. domain of your OWN app, the API dll will be forced to use .NET 2.0.

However, bear in mind that there are breaking changes between 1.1 and 2.0,
so your API might just crash.

<ngpo***@hotmail.com> wrote in message
Show quote

news:1150331329.683873.281030@r2g2000cwb.googlegroups.com...
>I am wanting to write an application and/or a Web service that will
> connect to another commercial application via that comercial
> application's API. I would like to write my application using VS.Net
> 2005 (as opposed to 2003). The commercial application can only run
> with the 1.1 Framework. Is there anyway to have my application utilize
> the 2.0 Framework but have the other application utilize the 1.1
> Framework when it is instantiated via it's API? Putting
> app_name.exe.config files in the application's folder works fine when
> launching that app via it's EXE but it seems that the API doesn't
> read those files.
>
> Thanks!!!
>