By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
457,949 Members | 1,426 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 457,949 IT Pros & Developers. It's quick & easy.

shared assemblies

P: n/a
Hello!

In directory c:\window\assembly(GAC) can you find a lot of global assembly
names which is called
shared assemblies.

If I for example use ILDASM on a file called Accessibility which is a dll
that exist in the c:\window\assembly(GAC) nothing happen why?

You can use ILDASM on any private assembly but it seems to be impossible on
any shared assembly

//Tony


Aug 22 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Tony,

What do you mean nothing happens? If you go and look in the GAC (you
are looking at a virtual view through a shell extension actually), it should
be there. Note, all assemblies in GAC need to be strong-named.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Tony Johansson" <jo*****************@telia.comwrote in message
news:Hc******************@newsb.telia.net...
Hello!

In directory c:\window\assembly(GAC) can you find a lot of global assembly
names which is called
shared assemblies.

If I for example use ILDASM on a file called Accessibility which is a dll
that exist in the c:\window\assembly(GAC) nothing happen why?

You can use ILDASM on any private assembly but it seems to be impossible
on any shared assembly

//Tony



Aug 22 '06 #2

P: n/a
Hello!
If I select a private assembly in ILDASM I get a lot of information listed
but if I select a shared assembly located at c:\window\assembly(GAC) I
get nothing listed.
So you mean this is normal not seeing anything when using ILDASM on any
shared assembly located in the GAC.

Now to my second question:
If I create a shared assembly from a private assembly and then use
properties
on this it shows for example the
codeBase:file:///C:/TEST_DLL/ClassLibrary3/bin/Release/classlibrary3.dll
but If I for example use properties on the Accessibility located in the
GAC this codeBase shows nothing why?
I mean the path to the actual Accessibility.dll should be displayed in the
codeBase when using the properties.

//Tony
"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.comskrev i
meddelandet news:Od**************@TK2MSFTNGP06.phx.gbl...
Tony,

What do you mean nothing happens? If you go and look in the GAC (you
are looking at a virtual view through a shell extension actually), it
should
be there. Note, all assemblies in GAC need to be strong-named.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Tony Johansson" <jo*****************@telia.comwrote in message
news:Hc******************@newsb.telia.net...
>Hello!

In directory c:\window\assembly(GAC) can you find a lot of global
assembly
>names which is called
shared assemblies.

If I for example use ILDASM on a file called Accessibility which is a
dll
>that exist in the c:\window\assembly(GAC) nothing happen why?

You can use ILDASM on any private assembly but it seems to be
impossible
>on any shared assembly

//Tony




Aug 22 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.