Hello,
I need to give full access to the code on my machine when I access it
through a share. It defaults to intranet zone and therefore is only
partially-trusted.
I want to have a constant mapped drive for all my developers, and I don't
want the overhead of maintaining the SUBST (DefineDosDevice
Thanx guys!
I've created a small standalone assembly that contains the interfaces and
am including it from both plugin and the service.
Thank you again.
I found myself laughing out loud as I got to the end of those instructions
:)
Clear as mud!
Tim McGee
Phoenix Controls, Software Engineering Group
mailto:[EMAIL PROTECTED]
978-795-3408
-Original Message-
From: Moderated discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On
Janis,
Mike's right in that you have two different interfaces.
Your solution is to declare the interface in a single place and use that
interface from both the service assembly and the plugin assembly.
The question is where you define the interface. I figure you have two
options:
1) Define the i
Hi Seref:
i recently had the same frustration as you debugging my ASP.NET web
service and then on into my vb6 COM DLL. after much much frustration and
research, i was actually willing to expire an MSDN incident to learn how
to do this. so, i opened a case with MS and i learned that there is no
way
> In order for plugin to compile, it declares IMaster interface in it's
> source, jsut like the Windows 2000 service does in it's
> source. Namespaces
> are identical.
That doesn't matter. You're bumping into the fact that types are scoped by the
assembly they're defined in. So two types that mi
Not sure if the subject describes my question very well. But here's the
info.
I've wrote a windows 2000 service. One of it's classes implements certain
Interface (IMaster).
Upon initiaization Windows 2000 service loads a plugin written in CSharp,
compiles it on the fly, loads the result assembly
Hi,
Currently i'm trying to implement a com interop project.My business logic is
implemented in a vb com dll, which i access from asp.net via com interop
Today, we had a serious problem and tried to debug the dll source. Even if i
managed to debug the vb dll from inside vs.net, the debugger acted s
