I have written my own custom server control based on Web Control. I placed
the .cs file in the App_Code Folder.

When I add the following tag prefix to my web.config I start seeing this
error (Design Time):

"Error Rendering Control - ButtonSearch An unhandled exception has
occurred. There was an error parsing the theme: The 'assembly' attribute
cannot be an empy string."
"Error Rendering Control - TextBoxSearch An unhandled exception has
occurred. There was an error parsing the theme: The 'assembly' attribute
cannot be an empy string."
"GridView - GridViewSearch Error was an error rendering the control - An
unhandled exception has occurred. There was an error parsing the theme:
The 'assembly' attribute cannot be an empy string."

I am seeing this error on all of the provided Microsoft Server Controls.
My custom server control appears to render and operate correctly.

Any Ideas??
<system.web>
<pages styleSheetTheme="Default">
<controls>
<add tagPrefix="myTag" namespace="my.WebControls" />
</controls>
</pages>
.. . .
<system.web>

thanks!

Hi Madhattan,

Welcome to ASPNET newsgroup.
From your description, you're using the
<system.web>
<pages styleSheetTheme="Default">
<controls>

setting to register some custom webcontrol prefixes in ASP.NET 2.0 web app
, however, you're getting the following error in design-time view:
===========
"Error Rendering Control - ButtonSearch An unhandled exception has
occurred. There was an error parsing the theme: The 'assembly' attribute
cannot be an empy string."
"Error Rendering Control - TextBoxSearch An unhandled exception has
occurred. There was an error parsing the theme: The 'assembly' attribute
cannot be an empy string."

==============

Based on my local test, for custom webserver control(not ascx usercontrol),
we can just add the below configuration in <controls> setting:

<add tagPrefix="acu" namespace="AppCustomControls" />
</controls>

No "assemlby" attributre needed if the code is put in App_Code dir... So
I think the problem is caused by something else. Also, you mentioned that
the control and page can work correctly at runtime, yes? Would you try
creating a new custom control and test to see whether it also cause such
behavior or test through a new web applicaiton project? If still get
problem, you can provide a simplified reproduce control so that we can also
perform some test on our side....

Thanks,

Steven Cheng
Microsoft Online Support

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



--------------------
| Reply-To: <madhattan@newsgroups.nospam>
| From: <madhattan@newsgroups.nospam>
| Subject: Error Rendering Control - ButtonSearch An unhandled exception
has occurred. There was an error parsing the theme: The 'assembly'
attribute cannot be an empy string
| Date: Tue, 13 Dec 2005 08:56:12 -0600
| Lines: 32
| Organization: madhattan@newsgroups.nospam
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| X-RFC2646: Format=Flowed; Original
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| Message-ID: <OmNGdV$$FHA.292@TK2MSFTNGP14.phx.gbl>
| Newsgroups: microsoft.public.dotnet.framework.aspnet.webcontrols
| NNTP-Posting-Host: umb53.oznet.ksu.edu 129.130.74.53
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl
microsoft.public.dotnet.framework.aspnet.webcontrols:31742
| X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webcontrols
|
| I have written my own custom server control based on Web Control. I
placed
| the .cs file in the App_Code Folder.
|
| When I add the following tag prefix to my web.config I start seeing this
| error (Design Time):
|
| "Error Rendering Control - ButtonSearch An unhandled exception has
| occurred. There was an error parsing the theme: The 'assembly'
attribute
| cannot be an empy string."
| "Error Rendering Control - TextBoxSearch An unhandled exception has
| occurred. There was an error parsing the theme: The 'assembly'
attribute
| cannot be an empy string."
| "GridView - GridViewSearch Error was an error rendering the control -
An
| unhandled exception has occurred. There was an error parsing the theme:
| The 'assembly' attribute cannot be an empy string."
|
| I am seeing this error on all of the provided Microsoft Server Controls.
| My custom server control appears to render and operate correctly.
|
| Any Ideas??
| <system.web>
| <pages styleSheetTheme="Default">
| <controls>
| <add tagPrefix="myTag" namespace="my.WebControls" />
| </controls>
| </pages>
| . . .
| <system.web>
|
| thanks!
|
|
|

Ok.
1) I created a new WebSite project.

2) Added a clean 'web.config'.

3) Added a new 'App_Code' folder.

4) Placed the 'MyServerControl.cs' in 'App_Code'

5) Placed the following in the 'web.config'
<system.web>
<pages>
<controls>
<add tagPrefix="myTag" namespace="my.WebControls" />
</controls>
</pages>
...
<system.web>

6) Everything in design view worked great! No Problems! Yea!

7) In 'web.config' I added the 'styleSheetTheme' to the <pages> node:
<system.web>
<pages styleSheetTheme="Default">
<controls>
<add tagPrefix="myTag" namespace="my.WebControls" />
</controls>
</pages>
...
<system.web>

6) The design time error: "Error Rendering Control..." came right back.

I still want to globally specify both the styleSheetTheme and control
tagPrefixes in the Web.Config. So the question becomes why do
Microsoft controls the screw-up design-time rendering when both
styleSheetTheme="Default" attribute and tagPrefix are used in a web.config.

Is there something that I am doing wrong or failing to consider?

Thanks again!




[quoted text, click to view]

Thanks for your quick response Madhattan,

I've got the problem and reproduced it on myside, it seems something
related to the "StyleSheetTheme" setting together with the custom control
prefix registring..... Currently I'm also not certain on the actual
cause, however, we can use the following things to make it work:

<pages styleSheetTheme="SimpleTheme" >
<controls >
<add tagPrefix="acu" namespace="AppCustomControls" assembly="App_Code" />
</controls>
</pages>

or

<pages styleSheetTheme="SimpleTheme" >
<controls >
<add tagPrefix="acu" namespace="AppCustomControls" assembly="__code" />
</controls>
</pages>


App_Code or __code can represent our asp.net 's dynamic compiled codes in
App_Code sub dir;....

Also, I'll forward this to our ASP.NET dev guys to see whether they've
addressed this problem or will have any action plan on this. I'll update
you as soon as I got any further info....

Thanks,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
--------------------
| Reply-To: <madhattan@newsgroups.nospam>
| From: <madhattan@newsgroups.nospam>
| References: <OmNGdV$$FHA.292@TK2MSFTNGP14.phx.gbl>
<$#PBptGAGHA.3764@TK2MSFTNGXA02.phx.gbl>
| Subject: Re: Error Rendering Control - ButtonSearch An unhandled
exception has occurred. There was an error parsing the theme: The
'assembly' attribute cannot be an empy string
| Date: Wed, 14 Dec 2005 09:57:46 -0600
| Lines: 158
| Organization: madhattan@newsgroups.nospam
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| X-RFC2646: Format=Flowed; Original
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| Message-ID: <ek77lcMAGHA.2036@TK2MSFTNGP14.phx.gbl>
| Newsgroups: microsoft.public.dotnet.framework.aspnet.webcontrols
| NNTP-Posting-Host: umb53.oznet.ksu.edu 129.130.74.53
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl
microsoft.public.dotnet.framework.aspnet.webcontrols:31779
| X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webcontrols
|
| Ok.
| 1) I created a new WebSite project.
|
| 2) Added a clean 'web.config'.
|
| 3) Added a new 'App_Code' folder.
|
| 4) Placed the 'MyServerControl.cs' in 'App_Code'
|
| 5) Placed the following in the 'web.config'
| <system.web>
| <pages>
| <controls>
| <add tagPrefix="myTag" namespace="my.WebControls" />
| </controls>
| </pages>
| ...
| <system.web>
|
| 6) Everything in design view worked great! No Problems! Yea!
|
| 7) In 'web.config' I added the 'styleSheetTheme' to the <pages> node:
| <system.web>
| <pages styleSheetTheme="Default">
| <controls>
| <add tagPrefix="myTag" namespace="my.WebControls" />
| </controls>
| </pages>
| ...
| <system.web>
|
| 6) The design time error: "Error Rendering Control..." came right back.
|
| I still want to globally specify both the styleSheetTheme and control
| tagPrefixes in the Web.Config. So the question becomes why do
| Microsoft controls the screw-up design-time rendering when both
| styleSheetTheme="Default" attribute and tagPrefix are used in a
web.config.
|
| Is there something that I am doing wrong or failing to consider?
|
| Thanks again!
|
|
|
|
[quoted text, click to view]
| > Hi Madhattan,
| >
| > Welcome to ASPNET newsgroup.
| > From your description, you're using the
| > <system.web>
| > <pages styleSheetTheme="Default">
| > <controls>
| >
| > setting to register some custom webcontrol prefixes in ASP.NET 2.0 web
app
| > , however, you're getting the following error in design-time view:
| > ===========
| > "Error Rendering Control - ButtonSearch An unhandled exception has
| > occurred. There was an error parsing the theme: The 'assembly'
attribute
| > cannot be an empy string."
| > "Error Rendering Control - TextBoxSearch An unhandled exception has
| > occurred. There was an error parsing the theme: The 'assembly'
attribute
| > cannot be an empy string."
| >
| > ==============
| >
| > Based on my local test, for custom webserver control(not ascx
| > usercontrol),
| > we can just add the below configuration in <controls> setting:
| >
| > <add tagPrefix="acu" namespace="AppCustomControls" />
| > </controls>
| >
| > No "assemlby" attributre needed if the code is put in App_Code dir...
So
| > I think the problem is caused by something else. Also, you mentioned
that
| > the control and page can work correctly at runtime, yes? Would you try
| > creating a new custom control and test to see whether it also cause such
| > behavior or test through a new web applicaiton project? If still get
| > problem, you can provide a simplified reproduce control so that we can
| > also
| > perform some test on our side....
| >
| > Thanks,
| >
| > Steven Cheng
| > Microsoft Online Support
| >
| > Get Secure! www.microsoft.com/security
| > (This posting is provided "AS IS", with no warranties, and confers no
| > rights.)
| >
| >
| >
| > --------------------
| > | Reply-To: <madhattan@newsgroups.nospam>
| > | From: <madhattan@newsgroups.nospam>
| > | Subject: Error Rendering Control - ButtonSearch An unhandled exception
| > has occurred. There was an error parsing the theme: The 'assembly'
| > attribute cannot be an empy string
| > | Date: Tue, 13 Dec 2005 08:56:12 -0600
| > | Lines: 32
| > | Organization: madhattan@newsgroups.nospam
| > | X-Priority: 3
| > | X-MSMail-Priority: Normal
| > | X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| > | X-RFC2646: Format=Flowed; Original
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| > | Message-ID: <OmNGdV$$FHA.292@TK2MSFTNGP14.phx.gbl>
| > | Newsgroups: microsoft.public.dotnet.framework.aspnet.webcontrols
| > | NNTP-Posting-Host: umb53.oznet.ksu.edu 129.130.74.53
| > | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
| > | Xref: TK2MSFTNGXA02.phx.gbl
| > microsoft.public.dotnet.framework.aspnet.webcontrols:31742
| > | X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webcontrols
| > |
| > | I have written my own custom server control based on Web Control. I
| > placed
| > | the .cs file in the App_Code Folder.
| > |
| > | When I add the following tag prefix to my web.config I start seeing
this
| > | error (Design Time):
| > |
| > | "Error Rendering Control - ButtonSearch An unhandled exception has
| > | occurred. There was an error parsing the theme: The 'assembly'
| > attribute

Hey Madhattan,

How are you doing on this, does the suggestion in my last reply helps a
little?
I've also confirmed with our dev team, they admit that this is a known
issue of the current page's design-time Theme parser.... And currently we
can workaround it by:

1. not using web.config Theme setting together with control assembly prefix
setting....

2. using the "__code" or "App_Code" as the "assembly" attribute value (for
those custom controls that put in App_Code folder...). The two keyword will
continue to be supported and can be used safely...

Thanks,

Steven Cheng
Microsoft Online Support

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



--------------------
| X-Tomcat-ID: 98342595
| References: <OmNGdV$$FHA.292@TK2MSFTNGP14.phx.gbl>
<$#PBptGAGHA.3764@TK2MSFTNGXA02.phx.gbl>
<ek77lcMAGHA.2036@TK2MSFTNGP14.phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: stcheng@online.microsoft.com (Steven Cheng[MSFT])
| Organization: Microsoft
| Date: Thu, 15 Dec 2005 04:58:48 GMT
| Subject: Re: Error Rendering Control - ButtonSearch An unhandled
exception has occurred. There was an error parsing the theme: The
'assembly' attribute cannot be an empy string
| X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webcontrols
| Message-ID: <WYOfDRTAGHA.1240@TK2MSFTNGXA02.phx.gbl>
| Newsgroups: microsoft.public.dotnet.framework.aspnet.webcontrols
| Lines: 200
| Path: TK2MSFTNGXA02.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl
microsoft.public.dotnet.framework.aspnet.webcontrols:31804
| NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182
|
| Thanks for your quick response Madhattan,
|
| I've got the problem and reproduced it on myside, it seems something
| related to the "StyleSheetTheme" setting together with the custom control
| prefix registring..... Currently I'm also not certain on the actual
| cause, however, we can use the following things to make it work:
|
| <pages styleSheetTheme="SimpleTheme" >
| <controls >
| <add tagPrefix="acu" namespace="AppCustomControls" assembly="App_Code"
/>
| </controls>
| </pages>
|
| or
|
| <pages styleSheetTheme="SimpleTheme" >
| <controls >
| <add tagPrefix="acu" namespace="AppCustomControls" assembly="__code" />
| </controls>
| </pages>
|
|
| App_Code or __code can represent our asp.net 's dynamic compiled codes in
| App_Code sub dir;....
|
| Also, I'll forward this to our ASP.NET dev guys to see whether they've
| addressed this problem or will have any action plan on this. I'll update
| you as soon as I got any further info....
|
| Thanks,
|
| Steven Cheng
| Microsoft Online Support
|
| Get Secure! www.microsoft.com/security
| (This posting is provided "AS IS", with no warranties, and confers no
| rights.)
| --------------------
| | Reply-To: <madhattan@newsgroups.nospam>
| | From: <madhattan@newsgroups.nospam>
| | References: <OmNGdV$$FHA.292@TK2MSFTNGP14.phx.gbl>
| <$#PBptGAGHA.3764@TK2MSFTNGXA02.phx.gbl>
| | Subject: Re: Error Rendering Control - ButtonSearch An unhandled
| exception has occurred. There was an error parsing the theme: The
| 'assembly' attribute cannot be an empy string
| | Date: Wed, 14 Dec 2005 09:57:46 -0600
| | Lines: 158
| | Organization: madhattan@newsgroups.nospam
| | X-Priority: 3
| | X-MSMail-Priority: Normal
| | X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
| | X-RFC2646: Format=Flowed; Original
| | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
| | Message-ID: <ek77lcMAGHA.2036@TK2MSFTNGP14.phx.gbl>
| | Newsgroups: microsoft.public.dotnet.framework.aspnet.webcontrols
| | NNTP-Posting-Host: umb53.oznet.ksu.edu 129.130.74.53
| | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
| | Xref: TK2MSFTNGXA02.phx.gbl
| microsoft.public.dotnet.framework.aspnet.webcontrols:31779
| | X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet.webcontrols
| |
| | Ok.
| | 1) I created a new WebSite project.
| |
| | 2) Added a clean 'web.config'.
| |
| | 3) Added a new 'App_Code' folder.
| |
| | 4) Placed the 'MyServerControl.cs' in 'App_Code'
| |
| | 5) Placed the following in the 'web.config'
| | <system.web>
| | <pages>
| | <controls>
| | <add tagPrefix="myTag" namespace="my.WebControls" />
| | </controls>
| | </pages>
| | ...
| | <system.web>
| |
| | 6) Everything in design view worked great! No Problems! Yea!
| |
| | 7) In 'web.config' I added the 'styleSheetTheme' to the <pages> node:
| | <system.web>
| | <pages styleSheetTheme="Default">
| | <controls>
| | <add tagPrefix="myTag" namespace="my.WebControls" />
| | </controls>
| | </pages>
| | ...
| | <system.web>
| |
| | 6) The design time error: "Error Rendering Control..." came right back.
| |
| | I still want to globally specify both the styleSheetTheme and control
| | tagPrefixes in the Web.Config. So the question becomes why do
| | Microsoft controls the screw-up design-time rendering when both
| | styleSheetTheme="Default" attribute and tagPrefix are used in a
| web.config.
| |
| | Is there something that I am doing wrong or failing to consider?
| |
| | Thanks again!
| |
| |
| |
| |
[quoted text, click to view]
| | > Hi Madhattan,
| | >
| | > Welcome to ASPNET newsgroup.
| | > From your description, you're using the
| | > <system.web>
| | > <pages styleSheetTheme="Default">
| | > <controls>
| | >
| | > setting to register some custom webcontrol prefixes in ASP.NET 2.0
web
| app
| | > , however, you're getting the following error in design-time view:
| | > ===========
| | > "Error Rendering Control - ButtonSearch An unhandled exception has
| | > occurred. There was an error parsing the theme: The 'assembly'
| attribute
| | > cannot be an empy string."
| | > "Error Rendering Control - TextBoxSearch An unhandled exception has
| | > occurred. There was an error parsing the theme: The 'assembly'
| attribute
| | > cannot be an empy string."
| | >
| | > ==============
| | >
| | > Based on my local test, for custom webserver control(not ascx
| | > usercontrol),
| | > we can just add the below configuration in <controls> setting:
| | >
| | > <add tagPrefix="acu" namespace="AppCustomControls" />
| | > </controls>
| | >
| | > No "assemlby" attributre needed if the code is put in App_Code dir...

| So
| | > I think the problem is caused by something else. Also, you mentioned
| that

Stephen,

I am having a similar problem, but I am not using custom controls from
the App_Code folder. Instead, I am simply using an asp:panel with
standard web controls contained inside.

To explain further, I began with a basic HTML table that contained a
series of Web Controls for user data input. Then, we needed a way to
override the standard HTML default button, so we implemented an
asp:panel with the DefaultButton option to control which button
submitted for the [Enter] key. Worked great!

However, after doing this work in the Visual Studio Source view of my
ASPX page, I tried to return to Design view and discovered that none of
the controls in my panel would render (though they had rendered fine
before implementing the panel). It appears that the problem is the
panel, because removing the panel fixes the design-time rendering
issue.

So, at the end of all this... I'm curious if the "ASP.NET dev guys"
that you referenced below might have a recommended fix for this. I
would appreciate any information that you could provide.

Thanks!
Jeff

Pariveda Solutions
2811 McKinney Ave. | Suite 220 LB126 | Dallas, Texas 75204

The Business of IT™
[url]www.parivedasolutions.com[/url]



--
jeff.townes
------------------------------------------------------------------------
Posted via http://www.codecomments.com
------------------------------------------------------------------------