Ask a Question related to ASP.NET Building Controls, Design and Development.
-
Riki #1
Re: Question on limiting choices in WebPart personalization
Just use an enum for the property.
--
Riki
"Ron Ruble" <RonRuble@discussions.microsoft.com> wrote in message
news:98C0D291-9C60-41B6-A639-44209DAA5025@microsoft.com...> I've created a WebPart, as a page using the designer, I'm looking at
> making
> it personalizable, and ran across these attributes:
>
> [Personalizable(), WebBrowsable, WebDisplayName("My Display Name")]
>
> all of which works great, making the properties available through a
> standard
> PropertyGridEditorPart. The WebBrowsable attribute makes it visible just
> fine; But I notice it uses the data type of the property to determine what
> type of control to display: bool gets a checkbox, string gets a free-form
> text box.
>
> Is there a way to display a list of available string choices in a list,
> without creating a personlization control? Something like a
> comma-separated
> list of values in an attribute I don't know about? Just looking for the
> easy
> way to do this. I can always read up on creating my own control if needed;
> I've seen the examples.
>
> Thanks for any ideas.
Riki Guest
-
Personalization extention
Hello, I am developing a site that will allow customers to personalize items. They will choose a background and then type in a name (or words)... -
Personalization Scope?
Hi All, I am not a programmer, but learning ASP.NET 2.0 to understand the capabilities and potential limitations for my customers. This is my... -
Interop.activeDS headache with Sharepoint v2 webpart
I've been working on a web part that will remind a user how many days they have until their password expires. I strong named it and created a... -
Scripting Question -- Limiting Form Input
Hi, See attached code. This will do the trick and hopefully is what your looking for. Regards, Dan. <script> function checkValue(theId) { -
Need to cache personalization data -- not sure which object to use
Hi Matt, Although this might be considered a matter of preference, I'd advise you to store "per user" information in Session. The Cache object is...



Reply With Quote

