Class library problem

[Guest]

Hello,

I have created a class library for connecting mobile devices to SQL Server
2000 and SQL Server 2005 Mobile databases. The library is one DLL file that
references SqlClient.dll and SqlCeServer.dll.
When I debug a mobile project and using the class library to connect to an
SQL Server 2005 Mobile, the system installs not only SQL Server 2005 Mobile
but also SQL Client for SQL Server 2000.
Is there any way to avoid installing the SQL Client for SQL Server 2000 or
do I need to create different libraries for both?

Thanks

 

[Daniel Moth]

When you say "the system installs" do you really mean, "VS2005 deploys"?
Also I presume that you don't have any runtime exceptions, just the
inconvenience of deploying extra stuff that you don't need, right?

If the answer is no to any of my assertions above then please elaborate.

If the answer to both is yes, then I don't think you can avoid this at
debugging time (short of using reflection for all your calls which is not
practical unless this is an academic exercise).

However, when you actually deploy through whatever mechanism you choose on
both platforms, then you can leave out the uneeded assemblies. As long as
your code doesn't result in any of it being loaded, you'll be fine.

Cheers
Daniel