Embedding <OBJECT> in ASP.NET

[Barrie Wilson]

anyone have any idea why I might be having an impossible time embedding a
YouTube <object> in an .ASPX file:

<object width="425" height="355">
<param name="movie"
value="

"></param>
<param name="wmode" value="transparent"></param>

<embed src="

"
type="application/x-shockwave-flash" wmode="transparent" width="425"
height="355"></embed>
</object>

(all just copied to the Clipboard from YouTube)

simple stuff ... never had a problem doing this on a web page; in VS 2005
it's hanging in design mode ... won't accept keystrokes, won't save the
file, etc ...

I also cannot figure how you embed WMP in an ASPX page ... I know people do
this stuff all the time

any suggestions?

TIA
BW

 

[PJ on Development]

Hi, BW

Have you tried to paste the code in the Source view and then saving
the file?

Regards,

Paulo Santos
http://pjondevelopment.50webs.com

 

[Guest]

As indicated, do this in source view and save the file. WMP can be embedded
with similar tags, there is an entire help section on MSDN for the Windows
Media SDK that has sample code.
-- Peter
http://www.eggheadcafe.com
unBlog: http://petesbloggerama.blogspot.com
BlogMetaFinder: http://www.blogmetafinder.com

 

[Barrie Wilson]

As indicated, do this in source view and save the file. WMP can be
embedded
with similar tags, there is an entire help section on MSDN for the Windows
Media SDK that has sample code.
-- Peter

thanks, Peter ... guess that makes the schmaltzy VS editor as good as
Notepad in this scenario ... oh well ... maybe VS 2008 will be a better
experience; this kind of thing was easy in FrontPage .... what happened?

 

[PJ on Development]

The point is that the VS really instantiate any component of the page
when working in Design view.

It's almost as working with an <DIV> with contentEditable='true'

So VS tries to instantiate the OBJECT and, probably, it's marked
somwhat unfave, and hence the error.

I don't knwo how FrontPage handled this kind of thing, but probably
the two development teams never got a chance to talk about it..

Regards,

Paulo Santos
http://pjondevelopment.50webs.com

 

[Barrie Wilson]

So VS tries to instantiate the OBJECT and, probably, it's marked
somwhat unfave, and hence the error.

yeah .... but it could at least be handled gracefully ...

I don't knwo how FrontPage handled this kind of thing, but probably
the two development teams never got a chance to talk about it..

wouldn't be the first time at Microsoft ... but maybe it was "intentional"
... as the Softies are so fond of saying these days