GAC and Ie WebControls

[Ignacio Martinez]

hey group!
I can't give the Microsoft.Web.UI.WebControls.dll assembly a strong name.

the SN.exe file doesn't throw any exception when I create the SNK file.

I created Strong Names for the rest of the DLL's of my Solution, and there
was no problem
the reason why I need to do this with the webcontrols assembly is that it's
required to build the solution once all the other assemblies have strong
names in the assemblyinfo.vb

any ideas???
thanx in advance, Ignacio,

 

[Neno Loje [MSP]]

Hi Ignacio,

the Microsoft.Web.UI.WebControls.dll has already a strong name!

Hope it helps,

Neno Loje
Microsoft Student Partner
University of Hamburg

 

[Ignacio Martinez]

well, according to the Visual Studio Assembly Properties, it hasn't.

if I run sn -T Microsoft.Web.UI.webControls.dll it says it doesn't have a
strong name.
and finally, and most important, if I run GACUTIL /i
Microsoft.Web.UI.webControls.dll it also says the assembly doesn't have a
strong name.
so, what's going on????

is there a way to manually give the assembly a strong name?
sn -k ..... shows no errors, but then I get the errors above.

any ideas?
thanx
Ignacio

 

[Conrad Zhang]

An assembly either has a strong name, or not.

And when it is compiled, you can't change it.

Why do you want to change Microsoft.Web.UI.WebControls.dll? Did you notify
your lawyer?

 

[Ignacio Martinez]

Well the thing is:

I'm trying to start Versioning my Application in order to deploy it to my
production server, and therefore apply the marvel known as "Shadow Copy" to
it. In my Web Application I have 5 projects, one ASP.NET, and 4 VB
Component Class Projects. (BackEnd and Business).
I edited the assemblyinfo.vb file on all projects and added strong names to
all Dll's succesfully, all added in GAC with no problem. The only assembly
that couldn't be strong named was MS IE WebControls's.
i realised this when I tried to build the App and the compiler output said
"The Microsoft.Web.UI.WebControls assembly does not have a strong name". If
I remove it from my ASP project References, it works fine, but that's not my
intention, since I use this Namespace often in all my ASPX files.

now that I have exposed my case, dear Conrad, do you understand what my
problem is?

I appreciate your response.
I hope someone has an idea, since Microsoft has ceased supporting the IE
WebControls.
Thanx in advance!!!!!!!!!
Nacho