Re: Override existing class name with custom assembly?

From: Thomas Christmann (thomas.christmann_at_online.de)
Date: 05/04/04 

Date: Tue, 4 May 2004 11:11:52 +0200

Hi!

> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/THCMCh09.asp
>
> They suggest sandboxing which wraps the OLE DB access code, give the wrapper
> full trust so OLE DB works, but the wrapper doesn't require callers to have
> full trust. Essentially you are loosening up OLE DB full trust requirement
> with your wrapper. This doesn't really help in your case though.

Well, yes, that's the article I read, and that's exactly what I'm trying to
do. But instead of sandboxing the DB calls from my App (like having an
assembly that takes some parameters, makes DB queries and resturns
strings), I was thinking about "sandboxing" the whole OleDb Namespace.
I know this will be incredibly hard to begin with, but another problem with
doing this, is that if applications have to use my new Namespace instead of
the old OleDb, I will run in all kinds of troubles because people tend to
develop their stuff at home (without my new namespace) and then upload to
my server (with my new namespace). So I either have the choice of making
the server believe my new namespace IS the old namespace (that's what I was
asking originally), or giving the client my new namespace, and make sure
that it integrates and works with the .NET GUI.

But yeah, I see this is getting harder and harder to do. Maybe one should
just wait for the next release of the .NET framework, where OleDb is
rumored to allow partially trusted callers...

Thanks,

Thomas

Relevant Pages

  • Re: Override existing class name with custom assembly?
    ... You could publish your OLE DB ... wrapper to your clients, available for download. ... > develop their stuff at home (without my new namespace) and then upload to ...
    (microsoft.public.dotnet.general)
  • C++ Managed Wrapper DLL exposes unmanaged names too - help
    ... classes using specific namespace but same class names as unmanaged. ... from the wrapping dll, thus hiding names of the wrapping namespace. ... one can only be accessed via "managedWrapper.sampleClass" from client ... What is the hint to overcome that - renaming all the wrapper of 7000 classes ...
    (microsoft.public.dotnet.framework.interop)
  • Re: [PATCH] private mounts
    ... >>I suppose it will be called by the login process or by wrappers like ... shell were actually modified to implement setnamespace, ... The wrapper I mentioned will usurally not be needed for normal operation, ... The mount would be a part of the current namespace, ...
    (Linux-Kernel)
  • problem with calling C++/CLI wrapper to C++ code from C# applicati
    ... only to the wrapper and the wrapper has a reference to unmanaged dll. ... reference only to the wrapper namespace. ... _CppLib = new CCppLib; ...
    (microsoft.public.dotnet.languages.vc)
  • Re: C runtime library for Unix
    ... and what I need to use to avoid polluting the user's namespace ... to route them through "wrapper" functions instead. ... namespace with CreateFile. ... You bought our system, ...
    (comp.lang.c)
Loading