In my VS/2003, the up and down arrows in the Custom Property Definition
Collection Editor have become disabled.

I could use them for ordering members of the collection before.  I don't
know when or why it happened, but the arrows don't respond anymore.

Has anyone had this problem?  How can I breathe life in them?

[ Post a follow-up to this message ]

Hi Bill,

these buttons are always disabled.
There is no way to sort custom properties.

Cheers,
Stefan.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

MCMS FAQ:
http://download.microsoft.com/downl...>
MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...nagement+Server
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------


"bill tie" <billtie@discussions.microsoft.com> wrote in message
news:9111C9EB-38C5-414B-B3CE-F332CAD2D9EE@microsoft.com...
>
> In my VS/2003, the up and down arrows in the Custom Property Definition
> Collection Editor have become disabled.
>
> I could use them for ordering members of the collection before.  I don't
> know when or why it happened, but the arrows don't respond anymore.
>
> Has anyone had this problem?  How can I breathe life in them?
>

[ Post a follow-up to this message ]

Stupid question... but is your template checked out?

bill tie wrote:
> In my VS/2003, the up and down arrows in the Custom Property
> Definition Collection Editor have become disabled.
>
> I could use them for ordering members of the collection before.  I
> don't know when or why it happened, but the arrows don't respond
> anymore.
>
> Has anyone had this problem?  How can I breathe life in them?

--
----------------------------------------------------------------------------
---------
Programming today is a race between software engineers
striving to build bigger and better idiot-proof programs,
and the Universe trying to produce bigger and better idiots.
So far, the Universe is winning.
-- Rich Cook

[ Post a follow-up to this message ]

> these buttons are always disabled.

I'd swear when I defined the first three custom properties I was able to
order them.  Later on, I've added more properties.  Now I'd like to re-order
them.

> There is no way to sort custom properties.

Bizarre.  Why are there the up and down arrows?  I'd like to loop through
some of them in my program.

Are you sure they can't be ordered using the arrows?

[ Post a follow-up to this message ]

Hi Bill,

this is a standard VS.NET dialog.
The buttons are always there.
If the collection allows sorting these arrows are enabled. If not, they are
disabled.
The MCMS collection for custom properties do not allow sorting so they are
disabled.

No idea why the VS.NET development team decided to disable them rather to
hide them.

Cheers,
Stefan.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

MCMS FAQ:
http://download.microsoft.com/downl...>
MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...nagement+Server
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------


"bill tie" <billtie@discussions.microsoft.com> wrote in message
news:BFFAA226-3F86-4754-ADAF-0A59AB0B6CD9@microsoft.com...
> 
>
> I'd swear when I defined the first three custom properties I was able to
> order them.  Later on, I've added more properties.  Now I'd like to
re-order
> them.
> 
>
> Bizarre.  Why are there the up and down arrows?  I'd like to loop through
> some of them in my program.
>
> Are you sure they can't be ordered using the arrows?
>

[ Post a follow-up to this message ]

However Bill, if your custom property was made of selected values, selected
values can be ordered... This is perhaps where you saw some ordering making
the confusion.

Cheers,

Cédric

Stefan [MSFT] wrote:[vbcol=seagreen]
> Hi Bill,
>
> this is a standard VS.NET dialog.
> The buttons are always there.
> If the collection allows sorting these arrows are enabled. If not,
> they are disabled.
> The MCMS collection for custom properties do not allow sorting so
> they are disabled.
>
> No idea why the VS.NET development team decided to disable them
> rather to hide them.
>
> Cheers,
> Stefan.
>
>
> "bill tie" <billtie@discussions.microsoft.com> wrote in message
> news:BFFAA226-3F86-4754-ADAF-0A59AB0B6CD9@microsoft.com... 

--
----------------------------------------------------------------------------
---------
Programming today is a race between software engineers
striving to build bigger and better idiot-proof programs,
and the Universe trying to produce bigger and better idiots.
So far, the Universe is winning.
-- Rich Cook

[ Post a follow-up to this message ]

Good point!
:-)

--
This posting is provided "AS IS" with no warranties, and confers no rights.

MCMS FAQ:
http://download.microsoft.com/downl...>
MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...nagement+Server
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------


"Cédric Dardenne" <cedric.nospam_dardenne@accenture.com> wrote in message
news:ebOXrj6rEHA.3244@tk2msftngp13.phx.gbl...
> However Bill, if your custom property was made of selected values,
selected
> values can be ordered... This is perhaps where you saw some ordering
making
> the confusion.
>
> Cheers,
>
> Cédric
>
> Stefan [MSFT] wrote: 
>
> --
> --------------------------------------------------------------------------
--
> ---------
> programming today is a race between software engineers
> striving to build bigger and better idiot-proof programs,
> and the Universe trying to produce bigger and better idiots.
> So far, the Universe is winning.
> -- Rich Cook
>
>

[ Post a follow-up to this message ]