the asp.net application doesnt compile it self under the /bin directory, where it is?

I want to use my custom control (.cs) in my web application. Custom control
is in the same assembly as my application. I want to know the name of the
assembly (.dll) file so i can add it's <@dotnet.itags.org.Pegister Assembly="abc.dll"> name.
But in asp.net 2.0 i can't find the assembly. It is not compiled under the
/bin folder. Where it is, or how can i give a reference to it?re:
> I want to use my custom control (.cs) in my web application.

Custom controls aren't located in *.cs files.
Classes are included in *.cs files.

Can you clarify what you are looking for ?

Juan T. Llibre, ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
ASPNETFAQ.COM : http://www.aspnetfaq.com/
Foros de ASP.NET en Espaol : http://asp.net.do/foros/
======================================
"Umut Tezduyar" <umut@dotnet.itags.org.tezduyar.com> wrote in message
news:uxcKX7t6FHA.2036@dotnet.itags.org.TK2MSFTNGP14.phx.gbl...
> I want to use my custom control (.cs) in my web application. Custom control is in the
> same assembly as my application. I want to know the name of the assembly (.dll) file so
> i can add it's <@dotnet.itags.org.Pegister Assembly="abc.dll"> name. But in asp.net 2.0 i can't find the
> assembly. It is not compiled under the /bin folder. Where it is, or how can i give a
> reference to it?
I mean, not the *.ascx (User controls), custom control.

Let me ask my question in this way: I can't add my custom control in a web
page because i don't know what to write in the <@dotnet.itags.org.Page Assembly=''> register
tag.

"Juan T. Llibre" <nomailreplies@dotnet.itags.org.nowhere.com> wrote in message
news:Oo7QLKu6FHA.2036@dotnet.itags.org.TK2MSFTNGP14.phx.gbl...
> re:
>> I want to use my custom control (.cs) in my web application.
> Custom controls aren't located in *.cs files.
> Classes are included in *.cs files.
> Can you clarify what you are looking for ?
>
> Juan T. Llibre, ASP.NET MVP
> ASP.NET FAQ : http://asp.net.do/faq/
> ASPNETFAQ.COM : http://www.aspnetfaq.com/
> Foros de ASP.NET en Espaol : http://asp.net.do/foros/
> ======================================
> "Umut Tezduyar" <umut@dotnet.itags.org.tezduyar.com> wrote in message
> news:uxcKX7t6FHA.2036@dotnet.itags.org.TK2MSFTNGP14.phx.gbl...
>>
>> I want to use my custom control (.cs) in my web application. Custom
>> control is in the same assembly as my application. I want to know the
>> name of the assembly (.dll) file so i can add it's <@dotnet.itags.org.Pegister
>> Assembly="abc.dll"> name. But in asp.net 2.0 i can't find the assembly.
>> It is not compiled under the /bin folder. Where it is, or how can i give
>> a reference to it?
OK...

For that, check out :
http://support.microsoft.com/defaul...kb;en-us;321749

The proper tag is :
<%@dotnet.itags.org. Register TagPrefix="Custom" Namespace="CustomControlNamespace" Assembly= "CustomControl" %
Custom is an alias that you associate with a namespace.
CustomControlNamespace is a namespace in which classes of an assembly are enclosed.
CustomControl is the name of the assembly file without an extension (.dll).

Juan T. Llibre, ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
ASPNETFAQ.COM : http://www.aspnetfaq.com/
Foros de ASP.NET en Espaol : http://asp.net.do/foros/
======================================
"Umut Tezduyar" <umut@dotnet.itags.org.tezduyar.com> wrote in message news:uI%23L45u6FHA.1000@dotnet.itags.org.tk2msftngp13.phx.gbl...
>I mean, not the *.ascx (User controls), custom control.
>
> Let me ask my question in this way: I can't add my custom control in a web
> page because i don't know what to write in the <@dotnet.itags.org.Page Assembly=''> register
> tag.
>
>
> "Juan T. Llibre" <nomailreplies@dotnet.itags.org.nowhere.com> wrote in message
> news:Oo7QLKu6FHA.2036@dotnet.itags.org.TK2MSFTNGP14.phx.gbl...
>> re:
>>> I want to use my custom control (.cs) in my web application.
>>
>> Custom controls aren't located in *.cs files.
>> Classes are included in *.cs files.
>>
>> Can you clarify what you are looking for ?

>> "Umut Tezduyar" <umut@dotnet.itags.org.tezduyar.com> wrote in message
>> news:uxcKX7t6FHA.2036@dotnet.itags.org.TK2MSFTNGP14.phx.gbl...
>>>
>>> I want to use my custom control (.cs) in my web application. Custom
>>> control is in the same assembly as my application. I want to know the
>>> name of the assembly (.dll) file so i can add it's <@dotnet.itags.org.Pegister
>>> Assembly="abc.dll"> name. But in asp.net 2.0 i can't find the assembly.
>>> It is not compiled under the /bin folder. Where it is, or how can i give
>>> a reference to it?
On Wed, 16 Nov 2005 10:52:05 -0800, "Umut Tezduyar"
<umut@dotnet.itags.org.tezduyar.com> wrote:

>I want to use my custom control (.cs) in my web application. Custom control
>is in the same assembly as my application.

Is this 2.0? (I assume so based on your previous questions). Your
custom control must be in App_Code, correct?

Something like this:

namespace OTC
{
public class MyCustomControl : WebControl
{
protected override void Render(HtmlTextWriter writer)
{
writer.Write("This is my custom control");
base.Render(writer);
}
}
}

>I want to know the name of the
>assembly (.dll) file so i can add it's <@dotnet.itags.org.Pegister Assembly="abc.dll"> name.
>But in asp.net 2.0 i can't find the assembly. It is not compiled under the
>/bin folder. Where it is, or how can i give a reference to it?

ASP.NET builds App_Code as a separate assembly, and the runtime will
recognize "App_Code" as an assembly name in a reference directive.

<%@dotnet.itags.org. Register Assembly="App_Code" TagPrefix="otc" Namespace="OTC" %
...

<otc:MyCustomControl runat="Server" id="boo" /
--
Scott
http://www.OdeToCode.com/blogs/scott/

the asp.net application doesn't compile it self under the /bin directory, where it is

I want to use my custom control (.cs) in my web application. Custom control
is in the same assembly as my application. I want to know the name of the
assembly (.dll) file so i can add it's <@dotnet.itags.org.Pegister Assembly="abc.dll"> name.
But in asp.net 2.0 i can't find the assembly. It is not compiled under the
/bin folder. Where it is, or how can i give a reference to it?re:
> I want to use my custom control (.cs) in my web application.
Custom controls aren't located in *.cs files.
Classes are included in *.cs files.
Can you clarify what you are looking for ?
Juan T. Llibre, ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
ASPNETFAQ.COM : http://www.aspnetfaq.com/
Foros de ASP.NET en Espaol : http://asp.net.do/foros/
======================================
"Umut Tezduyar" <umut@dotnet.itags.org.tezduyar.com> wrote in message
news:uxcKX7t6FHA.2036@dotnet.itags.org.TK2MSFTNGP14.phx.gbl...
> I want to use my custom control (.cs) in my web application. Custom contro
l is in the
> same assembly as my application. I want to know the name of the assembly (
.dll) file so
> i can add it's <@dotnet.itags.org.Pegister Assembly="abc.dll"> name. But in asp.net 2.0 i c
an't find the
> assembly. It is not compiled under the /bin folder. Where it is, or how ca
n i give a
> reference to it?
I mean, not the *.ascx (User controls), custom control.
Let me ask my question in this way: I can't add my custom control in a web
page because i don't know what to write in the <@dotnet.itags.org.Page Assembly=''> register
tag.
"Juan T. Llibre" <nomailreplies@dotnet.itags.org.nowhere.com> wrote in message
news:Oo7QLKu6FHA.2036@dotnet.itags.org.TK2MSFTNGP14.phx.gbl...
> re:
> Custom controls aren't located in *.cs files.
> Classes are included in *.cs files.
> Can you clarify what you are looking for ?
>
> Juan T. Llibre, ASP.NET MVP
> ASP.NET FAQ : http://asp.net.do/faq/
> ASPNETFAQ.COM : http://www.aspnetfaq.com/
> Foros de ASP.NET en Espaol : http://asp.net.do/foros/
> ======================================
> "Umut Tezduyar" <umut@dotnet.itags.org.tezduyar.com> wrote in message
> news:uxcKX7t6FHA.2036@dotnet.itags.org.TK2MSFTNGP14.phx.gbl...
>
OK...
For that, check out :
http://support.microsoft.com/defaul...kb;en-us;321749
The proper tag is :
<%@dotnet.itags.org. Register TagPrefix="Custom" Namespace="CustomControlNamespace" Assembly=
"CustomControl" %>
Custom is an alias that you associate with a namespace.
CustomControlNamespace is a namespace in which classes of an assembly are en
closed.
CustomControl is the name of the assembly file without an extension (.dll).
Juan T. Llibre, ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
ASPNETFAQ.COM : http://www.aspnetfaq.com/
Foros de ASP.NET en Espaol : http://asp.net.do/foros/
======================================
"Umut Tezduyar" <umut@dotnet.itags.org.tezduyar.com> wrote in message news:uI%23L45u6FHA.1000@dotnet.itags.org.tk2msftngp13.p
hx.gbl...
>I mean, not the *.ascx (User controls), custom control.
>
> Let me ask my question in this way: I can't add my custom control in a web
> page because i don't know what to write in the <@dotnet.itags.org.Page Assembly=''> registe
r
> tag.
>
>
> "Juan T. Llibre" <nomailreplies@dotnet.itags.org.nowhere.com> wrote in message
> news:Oo7QLKu6FHA.2036@dotnet.itags.org.TK2MSFTNGP14.phx.gbl...
On Wed, 16 Nov 2005 10:52:05 -0800, "Umut Tezduyar"
<umut@dotnet.itags.org.tezduyar.com> wrote:

>I want to use my custom control (.cs) in my web application. Custom control
>is in the same assembly as my application.
>
Is this 2.0? (I assume so based on your previous questions). Your
custom control must be in App_Code, correct?
Something like this:
namespace OTC
{
public class MyCustomControl : WebControl
{
protected override void Render(HtmlTextWriter writer)
{
writer.Write("This is my custom control");
base.Render(writer);
}
}
}

>I want to know the name of the
>assembly (.dll) file so i can add it's <@dotnet.itags.org.Pegister Assembly="abc.dll"> name.
>But in asp.net 2.0 i can't find the assembly. It is not compiled under the
>/bin folder. Where it is, or how can i give a reference to it?
>
ASP.NET builds App_Code as a separate assembly, and the runtime will
recognize "App_Code" as an assembly name in a reference directive.
<%@dotnet.itags.org. Register Assembly="App_Code" TagPrefix="otc" Namespace="OTC" %>
...
<otc:MyCustomControl runat="Server" id="boo" />
Scott
http://www.OdeToCode.com/blogs/scott/

the assembly 'ASPnetMenu' could not be loaded...

hello attach is a problem i'm having after deploying to the production
server. can someone please identify whats wrng with it?
all the required dll which was running on the development server was copied
into the production server even the aspnetmenu dll...
but i'm still having this problem...
=== Pre-bind state information ===
LOG: DisplayName = ASPnetMenu, Version=1.5.0.0, Culture=neutral,
PublicKeyToken=9bc9f846553156bb
(Fully-specified)
LOG: Appbase = file:///D:/App/GAR NPI2
LOG: Initial PrivatePath = bin
Calling assembly : NPI, Version=1.0.1924.37987, Culture=neutral,
PublicKeyToken=null.
===
LOG: Publisher policy file is not found.
LOG: No redirect found in host configuration file
(C:\WINDOWS\MICROS~1.NET\FRAMEW~1\V11~1.432\aspnet.config).
LOG: Using machine configuration file from
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\config\machine.config.
LOG: Post-policy reference: ASPnetMenu, Version=1.5.0.0, Culture=neutral,
PublicKeyToken=9bc9f846553156bb
LOG: Attempting download of new URL
file:///C:/WINDOWS/MICROS~1.NET/FRAMEW~1/V11~1.432/Temporary ASP.NET
Files/root/c3a69742/9fe93016/ASPnetMenu.DLL.
LOG: Attempting download of new URL
file:///C:/WINDOWS/MICROS~1.NET/FRAMEW~1/V11~1.432/Temporary ASP.NET
Files/root/c3a69742/9fe93016/ASPnetMenu/ASPnetMenu.DLL.
LOG: Attempting download of new URL file:///D:/App/GAR
NPI2/bin/ASPnetMenu.DLL.
WRN: Comparing the assembly name resulted in the mismatch: Minor VersionIs the application folder that has the "bin" folder where do you place the
aspnetmenu.dll, marked as an application in IIS? E.g is the bin folder at
correct level in the app hierarchy?
Teemu Keiski
ASP.NET MVP, AspInsider
Finland, EU
"Asha" <Asha@dotnet.itags.org.discussions.microsoft.com> wrote in message
news:6D1D936E-B0FC-445F-AC67-4B185123C343@dotnet.itags.org.microsoft.com...
> hello attach is a problem i'm having after deploying to the production
> server. can someone please identify whats wrng with it?
> all the required dll which was running on the development server was
> copied
> into the production server even the aspnetmenu dll...
> but i'm still having this problem...
> === Pre-bind state information ===
> LOG: DisplayName = ASPnetMenu, Version=1.5.0.0, Culture=neutral,
> PublicKeyToken=9bc9f846553156bb
> (Fully-specified)
> LOG: Appbase = file:///D:/App/GAR NPI2
> LOG: Initial PrivatePath = bin
> Calling assembly : NPI, Version=1.0.1924.37987, Culture=neutral,
> PublicKeyToken=null.
> ===
> LOG: Publisher policy file is not found.
> LOG: No redirect found in host configuration file
> (C:\WINDOWS\MICROS~1.NET\FRAMEW~1\V11~1.432\aspnet.config).
> LOG: Using machine configuration file from
> C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\config\machine.config.
> LOG: Post-policy reference: ASPnetMenu, Version=1.5.0.0, Culture=neutral,
> PublicKeyToken=9bc9f846553156bb
> LOG: Attempting download of new URL
> file:///C:/WINDOWS/MICROS~1.NET/FRAMEW~1/V11~1.432/Temporary ASP.NET
> Files/root/c3a69742/9fe93016/ASPnetMenu.DLL.
> LOG: Attempting download of new URL
> file:///C:/WINDOWS/MICROS~1.NET/FRAMEW~1/V11~1.432/Temporary ASP.NET
> Files/root/c3a69742/9fe93016/ASPnetMenu/ASPnetMenu.DLL.
> LOG: Attempting download of new URL file:///D:/App/GAR
> NPI2/bin/ASPnetMenu.DLL.
> WRN: Comparing the assembly name resulted in the mismatch: Minor Version
>
>

the assembly ASPnetMenu could not be loaded...

hello attach is a problem i'm having after deploying to the production
server. can someone please identify whats wrng with it?

all the required dll which was running on the development server was copied
into the production server even the aspnetmenu dll...

but i'm still having this problem...

=== Pre-bind state information ===
LOG: DisplayName = ASPnetMenu, Version=1.5.0.0, Culture=neutral,
PublicKeyToken=9bc9f846553156bb
(Fully-specified)
LOG: Appbase = file:///D:/App/GAR NPI2
LOG: Initial PrivatePath = bin
Calling assembly : NPI, Version=1.0.1924.37987, Culture=neutral,
PublicKeyToken=null.
===

LOG: Publisher policy file is not found.
LOG: No redirect found in host configuration file
(C:\WINDOWS\MICROS~1.NET\FRAMEW~1\V11~1.432\aspnet .config).
LOG: Using machine configuration file from
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\confi g\machine.config.
LOG: Post-policy reference: ASPnetMenu, Version=1.5.0.0, Culture=neutral,
PublicKeyToken=9bc9f846553156bb
LOG: Attempting download of new URL
file:///C:/WINDOWS/MICROS~1.NET/FRAMEW~1/V11~1.432/Temporary ASP.NET
Files/root/c3a69742/9fe93016/ASPnetMenu.DLL.
LOG: Attempting download of new URL
file:///C:/WINDOWS/MICROS~1.NET/FRAMEW~1/V11~1.432/Temporary ASP.NET
Files/root/c3a69742/9fe93016/ASPnetMenu/ASPnetMenu.DLL.
LOG: Attempting download of new URL file:///D:/App/GAR
NPI2/bin/ASPnetMenu.DLL.
WRN: Comparing the assembly name resulted in the mismatch: Minor VersionIs the application folder that has the "bin" folder where do you place the
aspnetmenu.dll, marked as an application in IIS? E.g is the bin folder at
correct level in the app hierarchy?

--
Teemu Keiski
ASP.NET MVP, AspInsider
Finland, EU

"Asha" <Asha@dotnet.itags.org.discussions.microsoft.com> wrote in message
news:6D1D936E-B0FC-445F-AC67-4B185123C343@dotnet.itags.org.microsoft.com...
> hello attach is a problem i'm having after deploying to the production
> server. can someone please identify whats wrng with it?
> all the required dll which was running on the development server was
> copied
> into the production server even the aspnetmenu dll...
> but i'm still having this problem...
> === Pre-bind state information ===
> LOG: DisplayName = ASPnetMenu, Version=1.5.0.0, Culture=neutral,
> PublicKeyToken=9bc9f846553156bb
> (Fully-specified)
> LOG: Appbase = file:///D:/App/GAR NPI2
> LOG: Initial PrivatePath = bin
> Calling assembly : NPI, Version=1.0.1924.37987, Culture=neutral,
> PublicKeyToken=null.
> ===
> LOG: Publisher policy file is not found.
> LOG: No redirect found in host configuration file
> (C:\WINDOWS\MICROS~1.NET\FRAMEW~1\V11~1.432\aspnet .config).
> LOG: Using machine configuration file from
> C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\confi g\machine.config.
> LOG: Post-policy reference: ASPnetMenu, Version=1.5.0.0, Culture=neutral,
> PublicKeyToken=9bc9f846553156bb
> LOG: Attempting download of new URL
> file:///C:/WINDOWS/MICROS~1.NET/FRAMEW~1/V11~1.432/Temporary ASP.NET
> Files/root/c3a69742/9fe93016/ASPnetMenu.DLL.
> LOG: Attempting download of new URL
> file:///C:/WINDOWS/MICROS~1.NET/FRAMEW~1/V11~1.432/Temporary ASP.NET
> Files/root/c3a69742/9fe93016/ASPnetMenu/ASPnetMenu.DLL.
> LOG: Attempting download of new URL file:///D:/App/GAR
> NPI2/bin/ASPnetMenu.DLL.
> WRN: Comparing the assembly name resulted in the mismatch: Minor Version

The check of the signature failed

Hi all,
Does someone know what this mean:
The check of the signature failed for assembly
'Infragistics.WebUI.UltraWebGrid.v2'
I also did a post to Infragistics but maybe this is a general problem
and someone can tell me about it?
Richard Loupatty
MIO Development
the NetherlandsHi Richard,
From your description, you encountered the "check for the signature failed
for assembly" error when calling a certain assembly in your asp.net web
application, yes?
Based on my research, this problem is likely caused by refererncing a
delaysigned assembly which is strong-named but haven't contained complete
signature.(This is mostly used for the dev version of a component be fore
it is released or shipped). Is the assembly you used
("Infragistics.WebUI") a 3rd-party one ? I think you can create a simple
winform application and reference this dll to see whether the problem also
occured. If also occurr, then I think you have the following choices:
1. Ask the assembly's developers for release version which has complete
signature contained. This is most recommended.
2. Still use this delaysigned one, but you need to turns off verification
for this assembly using the following command:
sn CVr myAssembly.dll
But this is only for developing, if you want to use the assembly in your
production, I strongly recommend that you choose the #1.
In addition, here is the reference in MSDN which has detailedly describe
the delaysign for an assembly:
#Delay Signing an Assembly
http://msdn.microsoft.com/library/e...ayedsigningasse
mbly.asp?frame=true
HOpe also helps. Thanks.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx
Steven,
Got the same aswer from Infragistics. It's a strong-name issue.
But the problem only occurs at my provider (shared hosting) when I ftp
the files.
Deploying it with a simple copy of all files to several test-servers
didn't give the error.
What could be the difference ?
Even when putting the following in the web.config doesn't solve the problem
<!-- This reference is OK, it specifies the full name of WebGrid. -->
<add assembly="Infragistics.WebUI.UltraWebGrid.v2, Version=2.0.5000.1,
Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb" />
"Steven Cheng[MSFT]" <v-schang@dotnet.itags.org.online.microsoft.com> schreef in bericht
news:30EYKX1IEHA.2432@dotnet.itags.org.cpmsftngxa06.phx.gbl...
> Hi Richard,
> From your description, you encountered the "check for the signature failed
> for assembly" error when calling a certain assembly in your asp.net web
> application, yes?
> Based on my research, this problem is likely caused by refererncing a
> delaysigned assembly which is strong-named but haven't contained complete
> signature.(This is mostly used for the dev version of a component be fore
> it is released or shipped). Is the assembly you used
> ("Infragistics.WebUI") a 3rd-party one ? I think you can create a simple
> winform application and reference this dll to see whether the problem also
> occured. If also occurr, then I think you have the following choices:
> 1. Ask the assembly's developers for release version which has complete
> signature contained. This is most recommended.
> 2. Still use this delaysigned one, but you need to turns off verification
> for this assembly using the following command:
> sn CVr myAssembly.dll
> But this is only for developing, if you want to use the assembly in your
> production, I strongly recommend that you choose the #1.
> In addition, here is the reference in MSDN which has detailedly describe
> the delaysign for an assembly:
> #Delay Signing an Assembly
>
http://msdn.microsoft.com/library/e...ayedsigningasse
> mbly.asp?frame=true
> HOpe also helps. Thanks.
> Regards,
> Steven Cheng
> Microsoft Online Support
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
> Get Preview at ASP.NET whidbey
> http://msdn.microsoft.com/asp.net/whidbey/default.aspx
>
Hi Richard,
I'm not sure whether you've turn off the verification off the certain
assembly on the server where it worked well. But as I mentioned in the last
reply, a delaysign assembly has no private key info in the meta data. So if
you configured it in configure file and use it as a Strong-named assembly,
it'll occur certain errors.
And this error can be disabled by turn off the verification for the
assembly by
sn CVr myAssembly.dll
as I mentioned.
So I think you can have a check to see whether you've turn this off. If
not, turn off the verification and test again to see whether the error
still occurs. Thanks.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx
It's clear to me now, but still doesn't work.
Could it be something at the provider's ?
"Steven Cheng[MSFT]" <v-schang@dotnet.itags.org.online.microsoft.com> schreef in bericht
news:iYEQ3zDJEHA.3064@dotnet.itags.org.cpmsftngxa10.phx.gbl...
> Hi Richard,
> I'm not sure whether you've turn off the verification off the certain
> assembly on the server where it worked well. But as I mentioned in the
last
> reply, a delaysign assembly has no private key info in the meta data. So
if
> you configured it in configure file and use it as a Strong-named assembly,
> it'll occur certain errors.
> And this error can be disabled by turn off the verification for the
> assembly by
> sn CVr myAssembly.dll
> as I mentioned.
> So I think you can have a check to see whether you've turn this off. If
> not, turn off the verification and test again to see whether the error
> still occurs. Thanks.
> Regards,
> Steven Cheng
> Microsoft Online Support
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
> Get Preview at ASP.NET whidbey
> http://msdn.microsoft.com/asp.net/whidbey/default.aspx
>
Hi Richard,
I'm not sure on the Provider but this is a potential cause. Also, it is it
possbile that you ask a release one( not compiled as delaysign) from the
provider? If so, I think that'll be nice. Do you think so?
Regards,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx
Steven,
Ok,
I installed a new version of Infragistics and it seems to work now.
But I still don't understand why it didn't work out with the old files.
if it's a 1 to 1 copy to the provider
Thanks for spending time on this !!
"Steven Cheng[MSFT]" <v-schang@dotnet.itags.org.online.microsoft.com> schreef in bericht
news:NQ51RFqJEHA.3064@dotnet.itags.org.cpmsftngxa10.phx.gbl...
> Hi Richard,
> I'm not sure on the Provider but this is a potential cause. Also, it is it
> possbile that you ask a release one( not compiled as delaysign) from the
> provider? If so, I think that'll be nice. Do you think so?
> Regards,
> Steven Cheng
> Microsoft Online Support
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
> Get Preview at ASP.NET whidbey
> http://msdn.microsoft.com/asp.net/whidbey/default.aspx
>

The check of the signature failed

Hi all,

Does someone know what this mean:

The check of the signature failed for assembly
'Infragistics.WebUI.UltraWebGrid.v2'

I also did a post to Infragistics but maybe this is a general problem
and someone can tell me about it?

Richard Loupatty

MIO Development
the NetherlandsHi Richard,

From your description, you encountered the "check for the signature failed
for assembly" error when calling a certain assembly in your asp.net web
application, yes?

Based on my research, this problem is likely caused by refererncing a
delaysigned assembly which is strong-named but haven't contained complete
signature.(This is mostly used for the dev version of a component be fore
it is released or shipped). Is the assembly you used
("Infragistics.WebUI") a 3rd-party one ? I think you can create a simple
winform application and reference this dll to see whether the problem also
occured. If also occurr, then I think you have the following choices:
1. Ask the assembly's developers for release version which has complete
signature contained. This is most recommended.

2. Still use this delaysigned one, but you need to turns off verification
for this assembly using the following command:
sn CVr myAssembly.dll
But this is only for developing, if you want to use the assembly in your
production, I strongly recommend that you choose the #1.

In addition, here is the reference in MSDN which has detailedly describe
the delaysign for an assembly:
#Delay Signing an Assembly
http://msdn.microsoft.com/library/e...ayedsigningasse
mbly.asp?frame=true

HOpe also helps. Thanks.

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx
Steven,

Got the same aswer from Infragistics. It's a strong-name issue.

But the problem only occurs at my provider (shared hosting) when I ftp
the files.

Deploying it with a simple copy of all files to several test-servers
didn't give the error.
What could be the difference ?

Even when putting the following in the web.config doesn't solve the problem

<!-- This reference is OK, it specifies the full name of WebGrid. -->
<add assembly="Infragistics.WebUI.UltraWebGrid.v2, Version=2.0.5000.1,
Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb" /
"Steven Cheng[MSFT]" <v-schang@dotnet.itags.org.online.microsoft.com> schreef in bericht
news:30EYKX1IEHA.2432@dotnet.itags.org.cpmsftngxa06.phx.gbl...
> Hi Richard,
> From your description, you encountered the "check for the signature failed
> for assembly" error when calling a certain assembly in your asp.net web
> application, yes?
> Based on my research, this problem is likely caused by refererncing a
> delaysigned assembly which is strong-named but haven't contained complete
> signature.(This is mostly used for the dev version of a component be fore
> it is released or shipped). Is the assembly you used
> ("Infragistics.WebUI") a 3rd-party one ? I think you can create a simple
> winform application and reference this dll to see whether the problem also
> occured. If also occurr, then I think you have the following choices:
> 1. Ask the assembly's developers for release version which has complete
> signature contained. This is most recommended.
> 2. Still use this delaysigned one, but you need to turns off verification
> for this assembly using the following command:
> sn CVr myAssembly.dll
> But this is only for developing, if you want to use the assembly in your
> production, I strongly recommend that you choose the #1.
> In addition, here is the reference in MSDN which has detailedly describe
> the delaysign for an assembly:
> #Delay Signing an Assembly
http://msdn.microsoft.com/library/e...ayedsigningasse
> mbly.asp?frame=true
> HOpe also helps. Thanks.
> Regards,
> Steven Cheng
> Microsoft Online Support
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
> Get Preview at ASP.NET whidbey
> http://msdn.microsoft.com/asp.net/whidbey/default.aspx
Hi Richard,

I'm not sure whether you've turn off the verification off the certain
assembly on the server where it worked well. But as I mentioned in the last
reply, a delaysign assembly has no private key info in the meta data. So if
you configured it in configure file and use it as a Strong-named assembly,
it'll occur certain errors.

And this error can be disabled by turn off the verification for the
assembly by
sn CVr myAssembly.dll
as I mentioned.

So I think you can have a check to see whether you've turn this off. If
not, turn off the verification and test again to see whether the error
still occurs. Thanks.

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx
It's clear to me now, but still doesn't work.
Could it be something at the provider's ?

"Steven Cheng[MSFT]" <v-schang@dotnet.itags.org.online.microsoft.com> schreef in bericht
news:iYEQ3zDJEHA.3064@dotnet.itags.org.cpmsftngxa10.phx.gbl...
> Hi Richard,
> I'm not sure whether you've turn off the verification off the certain
> assembly on the server where it worked well. But as I mentioned in the
last
> reply, a delaysign assembly has no private key info in the meta data. So
if
> you configured it in configure file and use it as a Strong-named assembly,
> it'll occur certain errors.
> And this error can be disabled by turn off the verification for the
> assembly by
> sn CVr myAssembly.dll
> as I mentioned.
> So I think you can have a check to see whether you've turn this off. If
> not, turn off the verification and test again to see whether the error
> still occurs. Thanks.
> Regards,
> Steven Cheng
> Microsoft Online Support
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
> Get Preview at ASP.NET whidbey
> http://msdn.microsoft.com/asp.net/whidbey/default.aspx
Hi Richard,

I'm not sure on the Provider but this is a potential cause. Also, it is it
possbile that you ask a release one( not compiled as delaysign) from the
provider? If so, I think that'll be nice. Do you think so?

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx
Steven,

Ok,

I installed a new version of Infragistics and it seems to work now.

But I still don't understand why it didn't work out with the old files.
if it's a 1 to 1 copy to the provider

Thanks for spending time on this !!

"Steven Cheng[MSFT]" <v-schang@dotnet.itags.org.online.microsoft.com> schreef in bericht
news:NQ51RFqJEHA.3064@dotnet.itags.org.cpmsftngxa10.phx.gbl...
> Hi Richard,
> I'm not sure on the Provider but this is a potential cause. Also, it is it
> possbile that you ask a release one( not compiled as delaysign) from the
> provider? If so, I think that'll be nice. Do you think so?
> Regards,
> Steven Cheng
> Microsoft Online Support
> Get Secure! www.microsoft.com/security
> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
> Get Preview at ASP.NET whidbey
> http://msdn.microsoft.com/asp.net/whidbey/default.aspx

The command prompt

following a book which says to use the command prompt to sign an assembly with a strong name. Im using visual studio for this project.

umm where can i find the command prompt to use for this?> umm where can i find the command promp

start->run->cmd.exe

j
You can either open the command prompt from within Visual Studio menu or Start -> Run -> cmd

Hope that helps
Kashif
Huh?
I thought you cant use regular DOS command prompt to sign an assembly. I alway use Visual Studio .NET command prompt.

The located assemblys manifest definition with name ExcelXmlWriter does not match the asse

Hi im getting the error

"The located assembly's manifest definition with name 'ExcelXmlWriter' does not match the assembly reference"

this happens when i tried to load a dll excelxmlwriter. it did not load properly in web matrix and gave the error that it cannot load.

thereafter when i hit the play button to view the page, i get the first error. I can however use the same files in IIS, which works fine. anyways i can use this dll. if not how do i get rid of this error? as i dnt want to publish each page to the web to test, i need to be able to view it once a i make a change.

ThanksI just got this error this morning. I'm afraid I have no idea how to solve it, but I have an idea of what it is about.

I think it is about version numbers for the NET framework. The problem I was having this morning was caused by the fact that I was using a dll for framework 1.1, when I only had framework 1.0.

My advice would be to check what framework you are using, and upgrade to 1.1 SP1.
Hi

I tried the service pack and it still does not work, this is so frustrating! Please someone give me an idea on what to do?

Thx