|
| Hi all,
Just wondering if anyone has a solution to this problem.
I've created a class library which encapsulates some logon code.
This library uses one of my registry classes as well as some ODBC
database access queries, so the top of the main code looks like this:
using System;
using System.Data.Odbc;
using RegistryAccess;
(Where RegistryAccess is my registry access namespace)
The problem arises when I add this class library to another solution,
it seems to share RegistryAccess with the parent solution, conflicting
with locally-included copies, producing compiler warnings like this:
c:\newcvs\server software\logon server\commondata.cs(97,17): warning
CS1595: 'RegistryAccess.clsRegistry' is defined in multiple places;
using definition from 'C:\newcvs\Common\clsRegistry.cs'
This is acceptable, since the compiler has chosen the correct one, but
I would still prefer that the namespace is kept out of the public view
of the class library.
Any ideas?
Cheers,
Alex.
Remove ernie and bert from email address to reply.
|
|