Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Newbie question

0 views
Skip to first unread message

Ed

unread,
May 14, 2004, 4:01:13 AM5/14/04
to
Just starting out with WSS . . . my WebPart needs an interface which contains a form. The examples I have seen all show the interface being created by building up a long string of HTML and then pumping that out to the interface using the RenderWebPart() method. Aside from my thoughts on that backwards step in web development, that is impracticle for me because I want to use ASP server controls in my webpart. The only option I can see is to use the inherited methods of the Control class to build the interface by dynamically adding child controls.

This seems to me to be a complicated way of doing what used to be a very simple task. It is the equivalent of writing an ASPX page by only using the code-behind . . . something that no developer in their right mind would do voluntarily, but as far as I can tell is being forced upon me in the WSS/WebParts world.

I suspect I must have missed at least one fundamental aspect of developing WebParts . . . I'll be very grateful if anyone has suggestions.

If I haven't misunderstood I'd be interested to hear other people's thoughts - am I alone in thinking there has got to be a better way to deliver HTML to a browser than this?

Ian Morrish

unread,
May 14, 2004, 4:36:03 PM5/14/04
to
Take a look at this http://www.reflectionit.nl/WebPart1.aspx
Regards,
Ian
"Ed" <ed@ejaN0_SP4Mconsulting.com> wrote in message
news:5441EA9B-7794-4A63...@microsoft.com...

Ian Morrish

unread,
May 15, 2004, 2:58:46 AM5/15/04
to
Take a look at this http://www.reflectionit.nl/WebPart1.aspx
Regards,
Ian

"Ed" <ed@ejaN0_SP4Mconsulting.com> wrote in message
news:5441EA9B-7794-4A63...@microsoft.com...

0 new messages