should i write my new component with .NET 2.0 ?

[Guest]

Hi,

I am writing a new networking component (dll).
I have a few questions :
1. if i write it with .NET 2 , am i decreasing the number of potentials
clients of my component ?
2. if the API to my component is compatible with .NET 1.1 but my component
use inside it .NET 2.0 , can a NET 1.1 clients use my component ? do they
need .NET 2 instalation ?

Thanks.

 

[Richard Blewett [DevelopMentor]]

Hi,

I am writing a new networking component (dll).
I have a few questions :
1. if i write it with .NET 2 , am i decreasing the number of potentials
clients of my component ?
2. if the API to my component is compatible with .NET 1.1 but my component
use inside it .NET 2.0 , can a NET 1.1 clients use my component ? do they
need .NET 2 instalation ?

Thanks.

..NET 2.0 components cannot be used on a 1.1 runtime but the reverse should
work (I say should because you won't know if there are issues until you test
the 1.1 components on version 2.0).

So, 1.1 clients can use your components but you have to make sure that the
2.0 runtime is loaded rather than the 1.1 - you cannot have two versions of
the runtime in a single process. You can force this using the supportRuntime
element in your app config file

Regards

Richard Blewett - DevelopMentor
http://www.dotnetconsult.co.uk/weblog
http://www.dotnetconsult.co.uk

 

[Guest]

1. You might be limiting the number of potential buyers. unless you need 2.0
functionality, stick with 1.1.

2. You can run 1.1 under 2.0, but will have to compile in 1.1 to run in 1.1
(2.0 compiled components will not work).

NOTE: You can build in 2.0, if you desire. You will have to avoid 2.0
specific features and create a 1.1 build script (batch file is fine) to
command line compile. This is one way to get the best of both worlds, the
other is just build in 1.1.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************