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

Help on <assemblies> key in web config file ???

P: n/a
Dear all,

I have read that instead of registering an assembly on the top a a page with
the Register directive we can use the <assembliea> section of Web config file
as follow :

<assemblies>
<add assembly="SharpUI.Input, Version=1.1.1.1220,
Culture=neutral,
PublicKeyToken=f517ee9424cd48d0"/>
</assemblies>

Then component within this assembly will be automatically register for
beeing used by all your application pages..

But then how can I use assembly components in my code? I thing I still need
to add my assembly as reference in my project or use the imports keywords ?

regards
serge
Nov 21 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
I believe this merely registers the assemblies so that they are visable in
your code. Much like going into VS.Net and click "Add Reference".

I believe what you want is to Register a namespace/assembly which contains
controls.

In 2.0 you can do this from the web.config, not in 1.x. Here's how you do it
in 2.0:

<pages>
<controls>
<add tagPrefix="X" namespace="XX" assembly="XXX" />
</controls>
</pages>
Karl

--
MY ASP.Net tutorials
http://www.openmymind.net/
http://openmymind.net/redirector.aspx?documentId=51 - Learn about AJAX!

"serge calderara" <se************@discussions.microsoft.com> wrote in
message news:55**********************************@microsof t.com...
Dear all,

I have read that instead of registering an assembly on the top a a page
with
the Register directive we can use the <assembliea> section of Web config
file
as follow :

<assemblies>
<add assembly="SharpUI.Input, Version=1.1.1.1220,
Culture=neutral,
PublicKeyToken=f517ee9424cd48d0"/>
</assemblies>

Then component within this assembly will be automatically register for
beeing used by all your application pages..

But then how can I use assembly components in my code? I thing I still
need
to add my assembly as reference in my project or use the imports keywords
?

regards
serge

Nov 21 '05 #2

P: n/a
No it is in ASP 1.1

What I have read is that for instance if you have an assembly in GAC and
components in this assembly will be used on several page in the web
application
then you should use the <add> key of the <assemblies> section in web.config
file.

It says that this way links the assembly to the application and make the
assembly availabale to all web form...

But then how to refer it in code as it is needed either to imports or add it
with reference ??

"Karl Seguin" wrote:
I believe this merely registers the assemblies so that they are visable in
your code. Much like going into VS.Net and click "Add Reference".

I believe what you want is to Register a namespace/assembly which contains
controls.

In 2.0 you can do this from the web.config, not in 1.x. Here's how you do it
in 2.0:

<pages>
<controls>
<add tagPrefix="X" namespace="XX" assembly="XXX" />
</controls>
</pages>
Karl

--
MY ASP.Net tutorials
http://www.openmymind.net/
http://openmymind.net/redirector.aspx?documentId=51 - Learn about AJAX!

"serge calderara" <se************@discussions.microsoft.com> wrote in
message news:55**********************************@microsof t.com...
Dear all,

I have read that instead of registering an assembly on the top a a page
with
the Register directive we can use the <assembliea> section of Web config
file
as follow :

<assemblies>
<add assembly="SharpUI.Input, Version=1.1.1.1220,
Culture=neutral,
PublicKeyToken=f517ee9424cd48d0"/>
</assemblies>

Then component within this assembly will be automatically register for
beeing used by all your application pages..

But then how can I use assembly components in my code? I thing I still
need
to add my assembly as reference in my project or use the imports keywords
?

regards
serge


Nov 21 '05 #3

P: n/a
Ok karl by referecing it I miss explain myself.

What I means is explain here at this link:
http://msdn.microsoft.com/library/de...onassembly.asp

Starting from here, What is the idea toi link an assembly to your
application at runtime, becasue anyway you will have to add a reference to
your project for using it ? this is what I do not really catch

"Karl Seguin" wrote:
I believe this merely registers the assemblies so that they are visable in
your code. Much like going into VS.Net and click "Add Reference".

I believe what you want is to Register a namespace/assembly which contains
controls.

In 2.0 you can do this from the web.config, not in 1.x. Here's how you do it
in 2.0:

<pages>
<controls>
<add tagPrefix="X" namespace="XX" assembly="XXX" />
</controls>
</pages>
Karl

--
MY ASP.Net tutorials
http://www.openmymind.net/
http://openmymind.net/redirector.aspx?documentId=51 - Learn about AJAX!

"serge calderara" <se************@discussions.microsoft.com> wrote in
message news:55**********************************@microsof t.com...
Dear all,

I have read that instead of registering an assembly on the top a a page
with
the Register directive we can use the <assembliea> section of Web config
file
as follow :

<assemblies>
<add assembly="SharpUI.Input, Version=1.1.1.1220,
Culture=neutral,
PublicKeyToken=f517ee9424cd48d0"/>
</assemblies>

Then component within this assembly will be automatically register for
beeing used by all your application pages..

But then how can I use assembly components in my code? I thing I still
need
to add my assembly as reference in my project or use the imports keywords
?

regards
serge


Nov 21 '05 #4

P: n/a
Serge:
I'm answering this in your other thread, 'cuz I think it's more relevant.

Anyone interested should look for Serge's post entitiled "Simple Question :
reference vs Register"

Karl

--
MY ASP.Net tutorials
http://www.openmymind.net/
"serge calderara" <se************@discussions.microsoft.com> wrote in
message news:43**********************************@microsof t.com...
Ok karl by referecing it I miss explain myself.

What I means is explain here at this link:
http://msdn.microsoft.com/library/de...onassembly.asp

Starting from here, What is the idea toi link an assembly to your
application at runtime, becasue anyway you will have to add a reference to
your project for using it ? this is what I do not really catch

"Karl Seguin" wrote:
I believe this merely registers the assemblies so that they are visable
in
your code. Much like going into VS.Net and click "Add Reference".

I believe what you want is to Register a namespace/assembly which
contains
controls.

In 2.0 you can do this from the web.config, not in 1.x. Here's how you do
it
in 2.0:

<pages>
<controls>
<add tagPrefix="X" namespace="XX" assembly="XXX" />
</controls>
</pages>
Karl

--
MY ASP.Net tutorials
http://www.openmymind.net/
http://openmymind.net/redirector.aspx?documentId=51 - Learn about AJAX!

"serge calderara" <se************@discussions.microsoft.com> wrote in
message news:55**********************************@microsof t.com...
> Dear all,
>
> I have read that instead of registering an assembly on the top a a page
> with
> the Register directive we can use the <assembliea> section of Web
> config
> file
> as follow :
>
> <assemblies>
> <add assembly="SharpUI.Input, Version=1.1.1.1220,
> Culture=neutral,
> PublicKeyToken=f517ee9424cd48d0"/>
> </assemblies>
>
> Then component within this assembly will be automatically register for
> beeing used by all your application pages..
>
> But then how can I use assembly components in my code? I thing I still
> need
> to add my assembly as reference in my project or use the imports
> keywords
> ?
>
> regards
> serge


Nov 21 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.