473,320 Members | 2,112 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,320 software developers and data experts.

Referencing assemblies and .config files.

Hi guys, just going through remoting at the moment and a couple of questions
relating to .net in general has surfaced.
Firstly I have seen in the designer that for the namespace and many of its
associated classes of System.Runtime.Remoting are available, but certain
ones are not. A reference to System.Runtime.Remoting needs to be added to
make available all the unavailable ones. Now although I (think) understand
the concept that an assembly needs to be referenced in order for its classes
and other members to be exposed to the designer, I cant quite get my head
around why some classes of certain namespaces are available and others
arent -until a reference is made to this assembly. Is this simply a design
issue that certain parts of a namespace have been exposed in certain
assemblies. Could someone explain how this works and why it has been done?

The second part of my question relates to XML elements and attributes of
config files. Having looked at an example of storing certain predefined
elements for remoting config it has occurred to me that there must be some
kind of reference for this XML based language to configure things at
runtime. For instance I might have known how to register a client activated
channel in c# code, but how would I have known that...
{snippet!!}
<channels>
<channel ref="http" port="1234" />
</channels>
...would have done the same thing. Therefore there must be somewhere that I
can look these things up?

thanks in advance!
--
Br,
Mark Broadbent
mcdba , mcse+i
=============
Nov 16 '05 #1
12 1924
1)
A namespace can be distributed over several assemblies. A namespace doesn't really exist in an assembly - each type in the assembly just happen to have a fully qualified name that consists of several parts. Therefore, it's possible that you see some System.Runtime.Remoting types in one assembly and others in another assembly.

However, I would expect all System.Runtime.Remoting.* types to be located in System.Runtime.Remoting.dll assembly, i.e., I don't understand how you can see some of the types without a reference to System.Runtime.Remoting.dll. Try to run ildasm.exe on the assemblies that you do have references to - and see what types they contain.

2)
I don't know where the reference is. But in addition to the "standard" stuff, it's possible to add your own configuration information in that file and then read it at runtime.

Christian

---

"Mark Broadbent" wrote:
Hi guys, just going through remoting at the moment and a couple of questions
relating to .net in general has surfaced.
Firstly I have seen in the designer that for the namespace and many of its
associated classes of System.Runtime.Remoting are available, but certain
ones are not. A reference to System.Runtime.Remoting needs to be added to
make available all the unavailable ones. Now although I (think) understand
the concept that an assembly needs to be referenced in order for its classes
and other members to be exposed to the designer, I cant quite get my head
around why some classes of certain namespaces are available and others
arent -until a reference is made to this assembly. Is this simply a design
issue that certain parts of a namespace have been exposed in certain
assemblies. Could someone explain how this works and why it has been done?

The second part of my question relates to XML elements and attributes of
config files. Having looked at an example of storing certain predefined
elements for remoting config it has occurred to me that there must be some
kind of reference for this XML based language to configure things at
runtime. For instance I might have known how to register a client activated
channel in c# code, but how would I have known that...
{snippet!!}
<channels>
<channel ref="http" port="1234" />
</channels>
...would have done the same thing. Therefore there must be somewhere that I
can look these things up?

thanks in advance!
--
Br,
Mark Broadbent
mcdba , mcse+i
=============

Nov 16 '05 #2
1. I think the trade-off of having some namespaces in separate assemblies is
really down to the size of the assembly and the likelihood that it will be
referenced. Loading an assembly takes time, so they want to reduce the size
of the default assemblies as much as possible. Namespaces like Remoting and
Windows.Forms are great candidates for splitting off into separate
assemblies because they are large namespaces and used only in specific
circumstances.

2. The remoting configuration file format is all documented in MSDN.
http://msdn.microsoft.com/library/en...asp?frame=true

--
John Wood
EMail: first name, dot, last name, at priorganize.com
"Mark Broadbent" <no************@no-spam-please.com> wrote in message
news:Ov**************@TK2MSFTNGP09.phx.gbl...
Hi guys, just going through remoting at the moment and a couple of questions relating to .net in general has surfaced.
Firstly I have seen in the designer that for the namespace and many of its
associated classes of System.Runtime.Remoting are available, but certain
ones are not. A reference to System.Runtime.Remoting needs to be added to
make available all the unavailable ones. Now although I (think) understand
the concept that an assembly needs to be referenced in order for its classes and other members to be exposed to the designer, I cant quite get my head
around why some classes of certain namespaces are available and others
arent -until a reference is made to this assembly. Is this simply a design
issue that certain parts of a namespace have been exposed in certain
assemblies. Could someone explain how this works and why it has been done?

The second part of my question relates to XML elements and attributes of
config files. Having looked at an example of storing certain predefined
elements for remoting config it has occurred to me that there must be some
kind of reference for this XML based language to configure things at
runtime. For instance I might have known how to register a client activated channel in c# code, but how would I have known that...
{snippet!!}
<channels>
<channel ref="http" port="1234" />
</channels>
..would have done the same thing. Therefore there must be somewhere that I
can look these things up?

thanks in advance!
--
Br,
Mark Broadbent
mcdba , mcse+i
=============

Nov 16 '05 #3
1. makes sense, thought that might be reason. Question is where am I picking
up the initial remoting classes from? -At a guess I'd say there is a
System.Runtime.Remoting namespace defined in mscorlib.dll (which I think Im
right in saying is referenced automatically). Certainly if I look at it thru
object browser it certainly seems that way.

2. Thx for this link. I was kind of hoping the documentation for all
namespaces/ classes config in Xml docs would be in one place but I guess
I'll have to see what I can find on a class by class basis. Still thx for
this starting point.

--
Br,
Mark Broadbent
mcdba , mcse+i
=============
"John Wood" <j@ro.com> wrote in message
news:uS**************@tk2msftngp13.phx.gbl...
1. I think the trade-off of having some namespaces in separate assemblies is really down to the size of the assembly and the likelihood that it will be
referenced. Loading an assembly takes time, so they want to reduce the size of the default assemblies as much as possible. Namespaces like Remoting and Windows.Forms are great candidates for splitting off into separate
assemblies because they are large namespaces and used only in specific
circumstances.

2. The remoting configuration file format is all documented in MSDN.
http://msdn.microsoft.com/library/en...asp?frame=true
--
John Wood
EMail: first name, dot, last name, at priorganize.com
"Mark Broadbent" <no************@no-spam-please.com> wrote in message
news:Ov**************@TK2MSFTNGP09.phx.gbl...
Hi guys, just going through remoting at the moment and a couple of

questions
relating to .net in general has surfaced.
Firstly I have seen in the designer that for the namespace and many of its associated classes of System.Runtime.Remoting are available, but certain
ones are not. A reference to System.Runtime.Remoting needs to be added to make available all the unavailable ones. Now although I (think) understand the concept that an assembly needs to be referenced in order for its

classes
and other members to be exposed to the designer, I cant quite get my head around why some classes of certain namespaces are available and others
arent -until a reference is made to this assembly. Is this simply a design issue that certain parts of a namespace have been exposed in certain
assemblies. Could someone explain how this works and why it has been done?
The second part of my question relates to XML elements and attributes of
config files. Having looked at an example of storing certain predefined
elements for remoting config it has occurred to me that there must be some kind of reference for this XML based language to configure things at
runtime. For instance I might have known how to register a client

activated
channel in c# code, but how would I have known that...
{snippet!!}
<channels>
<channel ref="http" port="1234" />
</channels>
..would have done the same thing. Therefore there must be somewhere that I can look these things up?

thanks in advance!
--
Br,
Mark Broadbent
mcdba , mcse+i
=============


Nov 16 '05 #4
1. thx. You'll see though that if you create a project and remove all
references, you can still access part of the System.Runtime.Remoting
namespace in code (try intellisense to see that it does) -I think these
types are in the mscorlib.dll.
--
Br,
Mark Broadbent
mcdba , mcse+i
=============
"Christian Heide Damm" <Ch****************@discussions.microsoft.com> wrote
in message news:E9**********************************@microsof t.com...
1)
A namespace can be distributed over several assemblies. A namespace doesn't really exist in an assembly - each type in the assembly just happen
to have a fully qualified name that consists of several parts. Therefore,
it's possible that you see some System.Runtime.Remoting types in one
assembly and others in another assembly.
However, I would expect all System.Runtime.Remoting.* types to be located in System.Runtime.Remoting.dll assembly, i.e., I don't understand how you
can see some of the types without a reference to
System.Runtime.Remoting.dll. Try to run ildasm.exe on the assemblies that
you do have references to - and see what types they contain.
2)
I don't know where the reference is. But in addition to the "standard" stuff, it's possible to add your own configuration information in that file
and then read it at runtime.
Christian

---

"Mark Broadbent" wrote:
Hi guys, just going through remoting at the moment and a couple of questions relating to .net in general has surfaced.
Firstly I have seen in the designer that for the namespace and many of its associated classes of System.Runtime.Remoting are available, but certain
ones are not. A reference to System.Runtime.Remoting needs to be added to make available all the unavailable ones. Now although I (think) understand the concept that an assembly needs to be referenced in order for its classes and other members to be exposed to the designer, I cant quite get my head around why some classes of certain namespaces are available and others
arent -until a reference is made to this assembly. Is this simply a design issue that certain parts of a namespace have been exposed in certain
assemblies. Could someone explain how this works and why it has been done?
The second part of my question relates to XML elements and attributes of
config files. Having looked at an example of storing certain predefined
elements for remoting config it has occurred to me that there must be some kind of reference for this XML based language to configure things at
runtime. For instance I might have known how to register a client activated channel in c# code, but how would I have known that...
{snippet!!}
<channels>
<channel ref="http" port="1234" />
</channels>
...would have done the same thing. Therefore there must be somewhere that I can look these things up?

thanks in advance!
--
Br,
Mark Broadbent
mcdba , mcse+i
=============

Nov 16 '05 #5
I think you'll find the remoting namespaces are held in a separate DLL
called System.Runtime.Remoting.dll.

--
John Wood
EMail: first name, dot, last name, at priorganize.com
"Mark Broadbent" <no************@no-spam-please.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
1. makes sense, thought that might be reason. Question is where am I picking up the initial remoting classes from? -At a guess I'd say there is a
System.Runtime.Remoting namespace defined in mscorlib.dll (which I think Im right in saying is referenced automatically). Certainly if I look at it thru object browser it certainly seems that way.

2. Thx for this link. I was kind of hoping the documentation for all
namespaces/ classes config in Xml docs would be in one place but I guess
I'll have to see what I can find on a class by class basis. Still thx for
this starting point.

--
Br,
Mark Broadbent
mcdba , mcse+i
=============
"John Wood" <j@ro.com> wrote in message
news:uS**************@tk2msftngp13.phx.gbl...
1. I think the trade-off of having some namespaces in separate assemblies
is
really down to the size of the assembly and the likelihood that it will be referenced. Loading an assembly takes time, so they want to reduce the size
of the default assemblies as much as possible. Namespaces like Remoting

and
Windows.Forms are great candidates for splitting off into separate
assemblies because they are large namespaces and used only in specific
circumstances.

2. The remoting configuration file format is all documented in MSDN.

http://msdn.microsoft.com/library/en...asp?frame=true

--
John Wood
EMail: first name, dot, last name, at priorganize.com
"Mark Broadbent" <no************@no-spam-please.com> wrote in message
news:Ov**************@TK2MSFTNGP09.phx.gbl...
Hi guys, just going through remoting at the moment and a couple of

questions
relating to .net in general has surfaced.
Firstly I have seen in the designer that for the namespace and many of

its associated classes of System.Runtime.Remoting are available, but certain ones are not. A reference to System.Runtime.Remoting needs to be added to make available all the unavailable ones. Now although I (think) understand the concept that an assembly needs to be referenced in order for its

classes
and other members to be exposed to the designer, I cant quite get my head around why some classes of certain namespaces are available and others
arent -until a reference is made to this assembly. Is this simply a design issue that certain parts of a namespace have been exposed in certain
assemblies. Could someone explain how this works and why it has been done?
The second part of my question relates to XML elements and attributes of config files. Having looked at an example of storing certain predefined elements for remoting config it has occurred to me that there must be some kind of reference for this XML based language to configure things at
runtime. For instance I might have known how to register a client

activated
channel in c# code, but how would I have known that...
{snippet!!}
<channels>
<channel ref="http" port="1234" />
</channels>
..would have done the same thing. Therefore there must be somewhere
that I can look these things up?

thanks in advance!
--
Br,
Mark Broadbent
mcdba , mcse+i
=============



Nov 16 '05 #6
There is some file that defines the _default switches_ for csc.exe. MsCorLib is certainly referenced by default.

If you try to run "csc.exe /nostdlib ....", then you'll probably get lots of compile errors since you're missing the basic stuff (e.g., Console.WriteLine).

Christian

---

"Mark Broadbent" wrote:
1. thx. You'll see though that if you create a project and remove all
references, you can still access part of the System.Runtime.Remoting
namespace in code (try intellisense to see that it does) -I think these
types are in the mscorlib.dll.
--
Br,
Mark Broadbent
mcdba , mcse+i
=============
"Christian Heide Damm" <Ch****************@discussions.microsoft.com> wrote
in message news:E9**********************************@microsof t.com...
1)
A namespace can be distributed over several assemblies. A namespace

doesn't really exist in an assembly - each type in the assembly just happen
to have a fully qualified name that consists of several parts. Therefore,
it's possible that you see some System.Runtime.Remoting types in one
assembly and others in another assembly.

However, I would expect all System.Runtime.Remoting.* types to be located

in System.Runtime.Remoting.dll assembly, i.e., I don't understand how you
can see some of the types without a reference to
System.Runtime.Remoting.dll. Try to run ildasm.exe on the assemblies that
you do have references to - and see what types they contain.

2)
I don't know where the reference is. But in addition to the "standard"

stuff, it's possible to add your own configuration information in that file
and then read it at runtime.

Christian

---

"Mark Broadbent" wrote:
Hi guys, just going through remoting at the moment and a couple of questions relating to .net in general has surfaced.
Firstly I have seen in the designer that for the namespace and many of its associated classes of System.Runtime.Remoting are available, but certain
ones are not. A reference to System.Runtime.Remoting needs to be added to make available all the unavailable ones. Now although I (think) understand the concept that an assembly needs to be referenced in order for its classes and other members to be exposed to the designer, I cant quite get my head around why some classes of certain namespaces are available and others
arent -until a reference is made to this assembly. Is this simply a design issue that certain parts of a namespace have been exposed in certain
assemblies. Could someone explain how this works and why it has been done?
The second part of my question relates to XML elements and attributes of
config files. Having looked at an example of storing certain predefined
elements for remoting config it has occurred to me that there must be some kind of reference for this XML based language to configure things at
runtime. For instance I might have known how to register a client activated channel in c# code, but how would I have known that...
{snippet!!}
<channels>
<channel ref="http" port="1234" />
</channels>
...would have done the same thing. Therefore there must be somewhere that I can look these things up?

thanks in advance!
--
Br,
Mark Broadbent
mcdba , mcse+i
=============


Nov 16 '05 #7
That was partly my point that you will notice that you can declaratively
access part of the System.Runtime.Remoting namespace *without* adding a
reference to the remoting.dll. However some classes of the namespace was
missing which I could only make available by referencing this dll. This
really is the basis for my question because (like your assumption) you would
have thought that everything that belongs to remoting would be accessible
through the remoting.dll; wheras you will find that alot is accessible
without referencing this. Hence I believe that this namespace spans several
dlls ... and the bit that is being exposed to me I think can be found in the
mscorlib.dll.
Please have a try with intellisense (or view mscorlib via object browser)
and you will see what I mean.
I can only assume that things have been designed like this to reduce file
library sizes, and to only expose essential classes in namespaces for design
reasons.

P.S. I am pretty sure that remoting is not the only namespace that spans
dlls like this.

I hope I made more sense.
--
Br,
Mark Broadbent
mcdba , mcse+i
=============
"John Wood" <j@ro.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl...
I think you'll find the remoting namespaces are held in a separate DLL
called System.Runtime.Remoting.dll.

--
John Wood
EMail: first name, dot, last name, at priorganize.com
"Mark Broadbent" <no************@no-spam-please.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl...
1. makes sense, thought that might be reason. Question is where am I picking
up the initial remoting classes from? -At a guess I'd say there is a
System.Runtime.Remoting namespace defined in mscorlib.dll (which I think

Im
right in saying is referenced automatically). Certainly if I look at it

thru
object browser it certainly seems that way.

2. Thx for this link. I was kind of hoping the documentation for all
namespaces/ classes config in Xml docs would be in one place but I guess
I'll have to see what I can find on a class by class basis. Still thx for
this starting point.

--
Br,
Mark Broadbent
mcdba , mcse+i
=============
"John Wood" <j@ro.com> wrote in message
news:uS**************@tk2msftngp13.phx.gbl...
1. I think the trade-off of having some namespaces in separate assemblies
is
really down to the size of the assembly and the likelihood that it will be referenced. Loading an assembly takes time, so they want to reduce the size
of the default assemblies as much as possible. Namespaces like
Remoting and
Windows.Forms are great candidates for splitting off into separate
assemblies because they are large namespaces and used only in specific
circumstances.

2. The remoting configuration file format is all documented in MSDN.

http://msdn.microsoft.com/library/en...asp?frame=true
--
John Wood
EMail: first name, dot, last name, at priorganize.com
"Mark Broadbent" <no************@no-spam-please.com> wrote in message
news:Ov**************@TK2MSFTNGP09.phx.gbl...
> Hi guys, just going through remoting at the moment and a couple of
questions
> relating to .net in general has surfaced.
> Firstly I have seen in the designer that for the namespace and many of
its
> associated classes of System.Runtime.Remoting are available, but certain > ones are not. A reference to System.Runtime.Remoting needs to be
added to
> make available all the unavailable ones. Now although I (think)

understand
> the concept that an assembly needs to be referenced in order for its
classes
> and other members to be exposed to the designer, I cant quite get my

head
> around why some classes of certain namespaces are available and
others > arent -until a reference is made to this assembly. Is this simply a

design
> issue that certain parts of a namespace have been exposed in certain
> assemblies. Could someone explain how this works and why it has been

done?
>
> The second part of my question relates to XML elements and

attributes of > config files. Having looked at an example of storing certain predefined > elements for remoting config it has occurred to me that there must

be some
> kind of reference for this XML based language to configure things at
> runtime. For instance I might have known how to register a client
activated
> channel in c# code, but how would I have known that...
> {snippet!!}
> <channels>
> <channel ref="http" port="1234" />
> </channels>
> ..would have done the same thing. Therefore there must be somewhere

that
I
> can look these things up?
>
> thanks in advance!
> --
>
>
> Br,
> Mark Broadbent
> mcdba , mcse+i
> =============
>
>



Nov 16 '05 #8
will try that sometime when Im not so busy. Thanks fo that tip -will be
interesting to see the results.

--
Br,
Mark Broadbent
mcdba , mcse+i
=============
"Christian Heide Damm" <Ch****************@discussions.microsoft.com> wrote
in message news:F5**********************************@microsof t.com...
There is some file that defines the _default switches_ for csc.exe. MsCorLib is certainly referenced by default.
If you try to run "csc.exe /nostdlib ....", then you'll probably get lots of compile errors since you're missing the basic stuff (e.g.,
Console.WriteLine).
Christian

---

"Mark Broadbent" wrote:
1. thx. You'll see though that if you create a project and remove all
references, you can still access part of the System.Runtime.Remoting
namespace in code (try intellisense to see that it does) -I think these
types are in the mscorlib.dll.
--
Br,
Mark Broadbent
mcdba , mcse+i
=============
"Christian Heide Damm" <Ch****************@discussions.microsoft.com> wrote in message news:E9**********************************@microsof t.com...
1)
A namespace can be distributed over several assemblies. A namespace

doesn't really exist in an assembly - each type in the assembly just happen to have a fully qualified name that consists of several parts. Therefore, it's possible that you see some System.Runtime.Remoting types in one
assembly and others in another assembly.

However, I would expect all System.Runtime.Remoting.* types to be located
in System.Runtime.Remoting.dll assembly, i.e., I don't understand how you can see some of the types without a reference to
System.Runtime.Remoting.dll. Try to run ildasm.exe on the assemblies that you do have references to - and see what types they contain.

2)
I don't know where the reference is. But in addition to the "standard"

stuff, it's possible to add your own configuration information in that file and then read it at runtime.

Christian

---

"Mark Broadbent" wrote:

> Hi guys, just going through remoting at the moment and a couple of

questions
> relating to .net in general has surfaced.
> Firstly I have seen in the designer that for the namespace and many
of its
> associated classes of System.Runtime.Remoting are available, but
certain > ones are not. A reference to System.Runtime.Remoting needs to be added to
> make available all the unavailable ones. Now although I (think)

understand
> the concept that an assembly needs to be referenced in order for its

classes
> and other members to be exposed to the designer, I cant quite get my

head
> around why some classes of certain namespaces are available and
others > arent -until a reference is made to this assembly. Is this simply a

design
> issue that certain parts of a namespace have been exposed in certain
> assemblies. Could someone explain how this works and why it has been

done?
>
> The second part of my question relates to XML elements and attributes of > config files. Having looked at an example of storing certain predefined > elements for remoting config it has occurred to me that there must

be some
> kind of reference for this XML based language to configure things at
> runtime. For instance I might have known how to register a client

activated
> channel in c# code, but how would I have known that...
> {snippet!!}
> <channels>
> <channel ref="http" port="1234" />
> </channels>
> ...would have done the same thing. Therefore there must be somewhere

that I
> can look these things up?
>
> thanks in advance!
> --
>
>
> Br,
> Mark Broadbent
> mcdba , mcse+i
> =============
>
>
>


Nov 16 '05 #9
Hi,

I believe that the classes, defined in mscorlib.dll are those parts of
the remoting, which make use of the cross appdomain buildin memory
channels, used behind the scenes, when you just pass a reference of an
object between 2 appdomains in your process, or those one, used for com
interop.

The other classes, which are responsible for creating channels and all
other remoting stuff are located at their own assembly.

Sunny
In article <#9**************@TK2MSFTNGP09.phx.gbl>, no-spam-please@no-
spam-please.com says...
1. thx. You'll see though that if you create a project and remove all
references, you can still access part of the System.Runtime.Remoting
namespace in code (try intellisense to see that it does) -I think these
types are in the mscorlib.dll.

Nov 16 '05 #10
Hi,

even so far noone from MS have confirmed this problem, it seems that it
exists and there is a memory leak when you use config files.

Please, read this article:

http://www.genuinechannels.com/Conte...x?id=88&type=1

Sunny

In article <#o**************@TK2MSFTNGP09.phx.gbl>, no-spam-please@no-
spam-please.com says...
1. makes sense, thought that might be reason. Question is where am I picking
up the initial remoting classes from? -At a guess I'd say there is a
System.Runtime.Remoting namespace defined in mscorlib.dll (which I think Im
right in saying is referenced automatically). Certainly if I look at it thru
object browser it certainly seems that way.

2. Thx for this link. I was kind of hoping the documentation for all
namespaces/ classes config in Xml docs would be in one place but I guess
I'll have to see what I can find on a class by class basis. Still thx for
this starting point.

Nov 16 '05 #11
Yep I agree. A lot of the remoting infrastructure is used for other things..
the real tcp channel management stuff is probably in the DLL.
That's the great thing about .net, the fact you can span one namespace over
multiple DLLs.

--
John Wood
EMail: first name, dot, last name, at priorganize.com

"Sunny" <su******@icebergwireless.com> wrote in message
news:eb**************@TK2MSFTNGP09.phx.gbl...
Hi,

I believe that the classes, defined in mscorlib.dll are those parts of
the remoting, which make use of the cross appdomain buildin memory
channels, used behind the scenes, when you just pass a reference of an
object between 2 appdomains in your process, or those one, used for com
interop.

The other classes, which are responsible for creating channels and all
other remoting stuff are located at their own assembly.

Sunny
In article <#9**************@TK2MSFTNGP09.phx.gbl>, no-spam-please@no-
spam-please.com says...
1. thx. You'll see though that if you create a project and remove all
references, you can still access part of the System.Runtime.Remoting
namespace in code (try intellisense to see that it does) -I think these
types are in the mscorlib.dll.

Nov 16 '05 #12
think that just about wraps that one up.

--
Br,
Mark Broadbent
mcdba , mcse+i
=============
"Mark Broadbent" <no************@no-spam-please.com> wrote in message
news:Ov**************@TK2MSFTNGP09.phx.gbl...
Hi guys, just going through remoting at the moment and a couple of questions relating to .net in general has surfaced.
Firstly I have seen in the designer that for the namespace and many of its
associated classes of System.Runtime.Remoting are available, but certain
ones are not. A reference to System.Runtime.Remoting needs to be added to
make available all the unavailable ones. Now although I (think) understand
the concept that an assembly needs to be referenced in order for its classes and other members to be exposed to the designer, I cant quite get my head
around why some classes of certain namespaces are available and others
arent -until a reference is made to this assembly. Is this simply a design
issue that certain parts of a namespace have been exposed in certain
assemblies. Could someone explain how this works and why it has been done?

The second part of my question relates to XML elements and attributes of
config files. Having looked at an example of storing certain predefined
elements for remoting config it has occurred to me that there must be some
kind of reference for this XML based language to configure things at
runtime. For instance I might have known how to register a client activated channel in c# code, but how would I have known that...
{snippet!!}
<channels>
<channel ref="http" port="1234" />
</channels>
..would have done the same thing. Therefore there must be somewhere that I
can look these things up?

thanks in advance!
--
Br,
Mark Broadbent
mcdba , mcse+i
=============

Nov 16 '05 #13

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

0
by: Gerard | last post by:
Hi, I am developing a set of assemblies which will be shared by many applications and so I intended to place them in the GAC at runtime. However, these assemblies have associated configuration...
16
by: PromisedOyster | last post by:
Hi I have a situation where I want to use circular referencing. I have cut down the example for demonstration purposes. Say we have one executable (main.exe) and two DLLS (A1.dll and A2.dll)....
9
by: Invalidlastname | last post by:
Hi, We developed some assemblies which use EnterpriseServices queued components. In order to use EnterpriseServices, these assemblies need to be installed into GAC. I used the pre-build and...
6
by: Sam-I-Am | last post by:
Hi There I have several websites that use shared assemblies in the GAC. When I try and update the GAC assemblies I get the following error: "The process cannot access the file because it is...
1
by: Shiraz | last post by:
Hi It seems like none of the old posts get any follow up after a few messages, whether or not something constructive comes out of them, so I'm left with no choice but to repost an earlier...
11
by: Jan | last post by:
I'm using the CSharpCodeProvider to buils some assemblies @ runtime which are never saved as files (cp.GenerateInMemory = true;). The generated assemblies are hierachically dependent on each other...
2
by: Smithers | last post by:
I have a Windows Forms application that implements a plug-in architecture whereby required assemblies are identified and loaded dynamically. Here are the relevant classes: A = application =...
1
by: Dave Anson | last post by:
What is the recommended practice for referencing assemblies in a project from other solutions? I am using Visual Studio 2005 Team System. I have several assemblies in another solution which will...
1
by: Tom | last post by:
My unsigned DLL works in my project that references it as long as I set Copy Local = true. Now I have signed the DLL with the sn.exe generated keys but have not yet moved the DLL into the GAC. ...
0
by: DolphinDB | last post by:
Tired of spending countless mintues downsampling your data? Look no further! In this article, you’ll learn how to efficiently downsample 6.48 billion high-frequency records to 61 million...
0
by: ryjfgjl | last post by:
ExcelToDatabase: batch import excel into database automatically...
0
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
1
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
0
by: ArrayDB | last post by:
The error message I've encountered is; ERROR:root:Error generating model response: exception: access violation writing 0x0000000000005140, which seems to be indicative of an access violation...
1
by: PapaRatzi | last post by:
Hello, I am teaching myself MS Access forms design and Visual Basic. I've created a table to capture a list of Top 30 singles and forms to capture new entries. The final step is a form (unbound)...
0
by: CloudSolutions | last post by:
Introduction: For many beginners and individual users, requiring a credit card and email registration may pose a barrier when starting to use cloud servers. However, some cloud server providers now...
0
by: Shællîpôpï 09 | last post by:
If u are using a keypad phone, how do u turn on JavaScript, to access features like WhatsApp, Facebook, Instagram....
0
by: Faith0G | last post by:
I am starting a new it consulting business and it's been a while since I setup a new website. Is wordpress still the best web based software for hosting a 5 page website? The webpages will be...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.