Connecting Tech Pros Worldwide Forums | Help | Site Map

GetAssemblies() & WebService...

Norm Dotti
Guest
 
Posts: n/a
#1: Jul 19 '05
I'm using the AppDomain.CurrentDomain.GetAssemblies()
method to obtain a list of currently loaded assemblies.
This returns the expected assembly name and version
values.
However, if I make a webservice call and then call
AppDomain.CurrentDomain.GetAssemblies() it returns an
additional assembly name, with gibberish values such
as "udmsmlb1", "janolvnq", etc. and always a version
number "0.0.0.0".

What is this additional value thats being returned?

TIA

Jon Skeet
Guest
 
Posts: n/a
#2: Jul 19 '05

re: GetAssemblies() & WebService...


Norm Dotti <normd@knorrassociates.com> wrote:[color=blue]
> I'm using the AppDomain.CurrentDomain.GetAssemblies()
> method to obtain a list of currently loaded assemblies.
> This returns the expected assembly name and version
> values.
> However, if I make a webservice call and then call
> AppDomain.CurrentDomain.GetAssemblies() it returns an
> additional assembly name, with gibberish values such
> as "udmsmlb1", "janolvnq", etc. and always a version
> number "0.0.0.0".
>
> What is this additional value thats being returned?[/color]

Are you doing anything like regular expressions, which may create a
temporary assembly for the compiled code? (I don't know for sure that
it does, but I wouldn't be surprised...)

--
Jon Skeet - <skeet@pobox.com>
http://www.pobox.com/~skeet/
If replying to the group, please do not mail me too
Anthony Moore
Guest
 
Posts: n/a
#3: Jul 19 '05

re: GetAssemblies() & WebService...


This would be because WebServices use XML Serialization, which works by
generating and loading a dynamically generated assembly. This provides
significant performance benefits to this type of serialization.

You should not really need to worry about this. If it is creating a leakage
situation for you, you can work around this by running the WebServices
calls in a different App-Domain which can then be unloaded.
--------------------[color=blue]
> Content-Class: urn:content-classes:message
> From: "Norm Dotti" <normd@knorrassociates.com>
> Sender: "Norm Dotti" <normd@knorrassociates.com>
> Subject: GetAssemblies() & WebService...
> Date: Thu, 10 Jul 2003 14:09:46 -0700
> Lines: 13
> Message-ID: <023101c34727$9732c790$a601280a@phx.gbl>
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: 7bit
> X-Newsreader: Microsoft CDO for Windows 2000
> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
> Thread-Index: AcNHJ5cyNXjwvYz3Rjehtzt4CyGVyA==
> Newsgroups: microsoft.public.dotnet.general
> Path: cpmsftngxa06.phx.gbl
> Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.general:100811
> NNTP-Posting-Host: TK2MSFTNGXA14 10.40.1.166
> X-Tomcat-NG: microsoft.public.dotnet.general
>
> I'm using the AppDomain.CurrentDomain.GetAssemblies()
> method to obtain a list of currently loaded assemblies.
> This returns the expected assembly name and version
> values.
> However, if I make a webservice call and then call
> AppDomain.CurrentDomain.GetAssemblies() it returns an
> additional assembly name, with gibberish values such
> as "udmsmlb1", "janolvnq", etc. and always a version
> number "0.0.0.0".
>
> What is this additional value thats being returned?
>
> TIA
>[/color]


--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

Norm Dotti
Guest
 
Posts: n/a
#4: Jul 19 '05

re: GetAssemblies() & WebService...


Using AppDomain.CurrentDomain.GetAssemblies() on the
client side does not return the Web Service assembly name
nor assemblies referenced by the webservice. Temporarily,
I've written a webmethod that returns assembly names and
versions in a dataset. I'd like to acheive this without
hitting the webservice. What is the best way to get web
reference assemblies and its referenced assemblies on the
client?

TIA
[color=blue]
>-----Original Message-----
>This would be because WebServices use XML Serialization,[/color]
which works by[color=blue]
>generating and loading a dynamically generated assembly.[/color]
This provides[color=blue]
>significant performance benefits to this type of[/color]
serialization.[color=blue]
>
>You should not really need to worry about this. If it is[/color]
creating a leakage[color=blue]
>situation for you, you can work around this by running[/color]
the WebServices[color=blue]
>calls in a different App-Domain which can then be[/color]
unloaded.[color=blue]
>--------------------[color=green]
>> Content-Class: urn:content-classes:message
>> From: "Norm Dotti" <normd@knorrassociates.com>
>> Sender: "Norm Dotti" <normd@knorrassociates.com>
>> Subject: GetAssemblies() & WebService...
>> Date: Thu, 10 Jul 2003 14:09:46 -0700
>> Lines: 13
>> Message-ID: <023101c34727$9732c790$a601280a@phx.gbl>
>> MIME-Version: 1.0
>> Content-Type: text/plain;
>> charset="iso-8859-1"
>> Content-Transfer-Encoding: 7bit
>> X-Newsreader: Microsoft CDO for Windows 2000
>> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
>> Thread-Index: AcNHJ5cyNXjwvYz3Rjehtzt4CyGVyA==
>> Newsgroups: microsoft.public.dotnet.general
>> Path: cpmsftngxa06.phx.gbl
>> Xref: cpmsftngxa06.phx.gbl[/color][/color]
microsoft.public.dotnet.general:100811[color=blue][color=green]
>> NNTP-Posting-Host: TK2MSFTNGXA14 10.40.1.166
>> X-Tomcat-NG: microsoft.public.dotnet.general
>>
>> I'm using the AppDomain.CurrentDomain.GetAssemblies()
>> method to obtain a list of currently loaded assemblies.
>> This returns the expected assembly name and version
>> values.
>> However, if I make a webservice call and then call
>> AppDomain.CurrentDomain.GetAssemblies() it returns an
>> additional assembly name, with gibberish values such
>> as "udmsmlb1", "janolvnq", etc. and always a version
>> number "0.0.0.0".
>>
>> What is this additional value thats being returned?
>>
>> TIA
>>[/color]
>
>
>--
>
>This posting is provided "AS IS" with no warranties, and[/color]
confers no rights.[color=blue]
>Use of included script samples are subject to the terms[/color]
specified at[color=blue]
>http://www.microsoft.com/info/cpyright.htm
>
>Note: For the benefit of the community-at-large, all[/color]
responses to this[color=blue]
>message are best directed to the newsgroup/thread from[/color]
which they[color=blue]
>originated.
>
>.
>[/color]
Anthony Moore
Guest
 
Posts: n/a
#5: Jul 21 '05

re: GetAssemblies() & WebService...


This would be best posted as a separate question on
microsoft.public.dotnet.framework.webservices

--------------------
| Content-Class: urn:content-classes:message
| From: "Norm Dotti" <normd@knorrassociates.com>
| Sender: "Norm Dotti" <normd@knorrassociates.com>
| References: <023101c34727$9732c790$a601280a@phx.gbl>
<yaVEYIzRDHA.2516@cpmsftngxa06.phx.gbl>
| Subject: RE: GetAssemblies() & WebService...
| Date: Fri, 11 Jul 2003 09:11:51 -0700
| Lines: 79
| Message-ID: <06ae01c347c7$23593a20$a001280a@phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcNHxyNZ7Z8xIARSTMuYhPKRAgTUmQ==
| Newsgroups: microsoft.public.dotnet.general
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.general:100897
| NNTP-Posting-Host: TK2MSFTNGXA08 10.40.1.160
| X-Tomcat-NG: microsoft.public.dotnet.general
|
| Using AppDomain.CurrentDomain.GetAssemblies() on the
| client side does not return the Web Service assembly name
| nor assemblies referenced by the webservice. Temporarily,
| I've written a webmethod that returns assembly names and
| versions in a dataset. I'd like to acheive this without
| hitting the webservice. What is the best way to get web
| reference assemblies and its referenced assemblies on the
| client?
|
| TIA
|
| >-----Original Message-----
| >This would be because WebServices use XML Serialization,
| which works by
| >generating and loading a dynamically generated assembly.
| This provides
| >significant performance benefits to this type of
| serialization.
| >
| >You should not really need to worry about this. If it is
| creating a leakage
| >situation for you, you can work around this by running
| the WebServices
| >calls in a different App-Domain which can then be
| unloaded.
| >--------------------
| >> Content-Class: urn:content-classes:message
| >> From: "Norm Dotti" <normd@knorrassociates.com>
| >> Sender: "Norm Dotti" <normd@knorrassociates.com>
| >> Subject: GetAssemblies() & WebService...
| >> Date: Thu, 10 Jul 2003 14:09:46 -0700
| >> Lines: 13
| >> Message-ID: <023101c34727$9732c790$a601280a@phx.gbl>
| >> MIME-Version: 1.0
| >> Content-Type: text/plain;
| >> charset="iso-8859-1"
| >> Content-Transfer-Encoding: 7bit
| >> X-Newsreader: Microsoft CDO for Windows 2000
| >> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| >> Thread-Index: AcNHJ5cyNXjwvYz3Rjehtzt4CyGVyA==
| >> Newsgroups: microsoft.public.dotnet.general
| >> Path: cpmsftngxa06.phx.gbl
| >> Xref: cpmsftngxa06.phx.gbl
| microsoft.public.dotnet.general:100811
| >> NNTP-Posting-Host: TK2MSFTNGXA14 10.40.1.166
| >> X-Tomcat-NG: microsoft.public.dotnet.general
| >>
| >> I'm using the AppDomain.CurrentDomain.GetAssemblies()
| >> method to obtain a list of currently loaded assemblies.
| >> This returns the expected assembly name and version
| >> values.
| >> However, if I make a webservice call and then call
| >> AppDomain.CurrentDomain.GetAssemblies() it returns an
| >> additional assembly name, with gibberish values such
| >> as "udmsmlb1", "janolvnq", etc. and always a version
| >> number "0.0.0.0".
| >>
| >> What is this additional value thats being returned?
| >>
| >> TIA
| >>
| >
| >
| >--
| >
| >This posting is provided "AS IS" with no warranties, and
| confers no rights.
| >Use of included script samples are subject to the terms
| specified at
| >http://www.microsoft.com/info/cpyright.htm
| >
| >Note: For the benefit of the community-at-large, all
| responses to this
| >message are best directed to the newsgroup/thread from
| which they
| >originated.
| >
| >.
| >
|

Closed Thread


Similar .NET Framework bytes