Attribute 'Title' is not a valid attribute of element 'ProviderWebPart' etc..

R

rote

I have a webpart project i copied across and after setting up in VS 2005 all good.
When i go to the design mode and try and autofornat my webpartzone to for example Simple or Professional.
The i try and view it to Design mode i get error saying it can't be switched and then when i complile it i get these errors below !!! arg..

Attribute 'width' is considered outdated. A newer construct is recommended.
Attribute 'Title' is not a valid attribute of element 'ProviderWebPart'.

How can i get rid of these stuff.
Any ideas
 
M

Michael Nemtsev [MVP]

Hello rote,

What the doc type settings do you have and which superclass of webpart you
are using?!

Seems that you have .net 1.1 webpart, not 2.0 one

---
WBR,
Michael Nemtsev [Microsoft MVP] :: blog: http://spaces.live.com/laflour
:: http://twitter.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo


r> I have a webpart project i copied across and after setting up in VS
r> 2005 all good.
r>
r> When i go to the design mode and try and autofornat my webpartzone to
r> for example Simple or Professional.
r>
r> The i try and view it to Design mode i get error saying it can't be
r> switched and then when i complile it i get these errors below !!!
r> arg..
r>
r> Attribute 'width' is considered outdated. A newer construct is
r> recommended. Attribute 'Title' is not a valid attribute of element
r> 'ProviderWebPart'.
r>
r> How can i get rid of these stuff.
r> Any idea
 
R

rote

When i create a new webform and add Wepart components.
and Use the autoformat option it does work well and i can switch btw design
and code
I reckon it an old project and i have to re-create it.
Anyways to correct this without creating a new project?
Michael you do reisde in Melb isn't it.Do you attend MOSSIG :)
 
M

Michael Nemtsev [MVP]

Hello rote,

r> When i create a new webform and add Wepart components.
r> and Use the autoformat option it does work well and i can switch btw
r> design
r> and code
r> I reckon it an old project and i have to re-create it.
r> Anyways to correct this without creating a new project?

Seems that some of old classes is uses, which are outdated in new solution.

Compare what the difference in page from new solution and in old one


r> Michael you do reisde in Melb isn't it.Do you attend MOSSIG :)

Nope, I'm Sydney based :)


---
WBR,
Michael Nemtsev [Microsoft MVP] :: blog: http://spaces.live.com/laflour
:: http://twitter.com/laflour

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Validation (XHTML 1.0 Transitional) - Attribute..... is not a valid attribute of..... 2
attribute or is not a valid attribute od element ListItem 2
Attribute 'onchange' is not a valid attribute of element 'TextBox' 2
Attribute 'ms_2d_layout' is not a valid attribute of element 'tabl 4
Validation (XHTML 1.0 Transitional): Attribute 'height' is not a valid attribute of element 'table' 1
Attribute 'ms_2d_layout' is not a valid attribute of element 'table' 4
Validation (Internet Explorer 6): Attribute 'target' is not a valid attributeof element 'frame' 1
validation(asp.net):attribution onblur is not a valid attribute of 1

Members online

No members online now.
Total: 80 (members: 0, guests: 80)
Robots: 249

Forum statistics

Threads
473,982
Messages
2,570,185
Members
46,736
Latest member
AdolphBig6

Latest Threads

Top