not answering your questions directly but another option is to define
the datasource in the markup and link it to the combobox which lets
you change the property names without needing to regenerate the
assembly.
On Wed, May 26, 2010 at 8:35 AM, Winston Pang winstonp...@gmail.com wrote:
Hi guys,
Their issue is refactoring, when changing the type names, string's won't be
part of refactoring.
I have put them in the markup whenever possible, however there are
instances, where I have to do it int he code behind, as the third party
control, requires me to hook into an event to retrieve this
On Wed, May 26, 2010 at 8:35 AM, Winston Pang winstonp...@gmail.com wrote:
Hi guys,
This is more of a question of whether or not this sounds feasible and has
anyone seen anyone do this:
Typically with most ASP.NET controls, lets take the ComboBox for an example,
it'll be like
On 26 May 2010 08:35, Winston Pang winstonp...@gmail.com wrote:
Hi guys,
This is more of a question of whether or not this sounds feasible and has
anyone seen anyone do this:
Typically with most ASP.NET controls, lets take the ComboBox for an example,
it'll be like
Well, firstly. The client is govt, and we're really dealing with their
internal IT team, who would eventually do supporting for the system.
I have no say in whether we do it or not, I've told them, it's redundant,
and uncommon, and a bit too much. I've done all I can, can't fight anymore
about
Or
Just an opportunity to do something different, that is what they want
that is what we will give them,
or even better ask them why? where did they get the idea to have it
like that from and understand their real concerns that has facilitated
the odd requirements, maybe there is method to their
