We don't have the luxuary of turning off  AllowShowAllRowsOnDropDown as it's required for our implementation.  Don't you think I've looked at the examples?  They're not very helpful.  You know the issue we have here and you can create a sample that more precisely targets our needs for this issue.  Why do you seem so reluctant to provide a sample?  Also, have you sent the request to development letting them know we need this feature?  If not, can you please do so ASAP?  We already have our application in production and need this taken care of.  We can't be changing our entire architecture at this point in the game for something, as I already stated, the control should be able to do.

If you're not able to address this issue, then please escalate it to someone who can.  Thank you.

Hello Handy,

It may not be a bug, but it's definitely an issue we need to resolve immediately please.

So are you saying we can't achieve what we need automatically by the WebCombo control?  We'll have to write our own data load procedure?  I hope that's not the case for such a simple and obvious feature that should be part of the default behavior of the control.  Would you please modify my sample to show how this is done?

I'll change how the code is set up in the sample and let you know how it works.  Also, what is "this event" that you refer to which will be called?  I looked at all the events in WebCombo that can be overriden and did not find any event for LoadOnDemand.

Hi Riendy,

It'll be difficult to provide a sample as this problem is not consistent.  But like I said in my initial email, it's not the problem with the assembly itself and it's not really an Intersoft problem.  Although that may not be a 100% certainty, but let us go with that premise for now.

There are two separate issues I see here:

1. Why is this WinUI assembly needed for web-based controls?  We don't use any WinForms and Windows UI components so we'd like to know why this is needed.  I'm assuming this is a WinForms assembly based on the naming.
2. Microsoft has identified the source being assemblies that are .NET 1.1.  With that being the case, can't you guys just provide a new version of this assembly compiled under, at minimum, the .NET Framework 2.0?  I know that 2.0 was a major upgrade over 1.1 so I can understand that it may require more than just a simple recompile, but now that .NET is up to version 4.0, it's probably time to get rid of any 1.1 assemblies to avoid future problems anyway don't you agree?

You can easily create your own VS2008 solution with some custom control projects (just create some dummy controls that derive from existing classes like TextBox, Label, etc.) and a web applicaton project (NOT web site) with several ASPX pages.  Then convert it to VS2010, then attempt to make updates to the aspx pages.  Right now I just don't have the time to create a sample for you as it's a bit time consuming.

No, this issue is NOT related, directly anyway, to the other one, however, we do need help on resolving the other issue Yudi is working on since we're still on VS2008.

I'd be happy to show you, via webex, if you'd like the other issue, however, I've already provided video and samples.

With this issue, it's going to require involving Microsoft as well.  Right now, unfortunately, I don't have the time to spend on this one.  It may be a few weeks until I'm free to devote time to this one, so e can touch base again at that time.

Essentially, when you update ASPX markup code, what happens is that the designer is not updated correctly with the control.  So, for example, if we add our own custom text box, say PrismVirtualTextBox from an assembly namespace called PRISM.VirtualInterface, the designer file woudl be incorrectly updated with the object from the wrong namespace, e.g., PRISM.BusinessLogic.PrismVirtualTextBox.

If you're attempting to duplicate, you'll have to create a solution with custom control classes and some "dummy" classes that are under the same top namespace in VS2008 first.  After you set up the test, you'll need to then upgrade your solution to VS2010 and then make updates to your ASPX code.  it may work for a while so you have to keep making updates until it breaks.  It may take several tries like it did with us.

Yudi,

I created one more sample that more closely reflects how we do things in our app as it's heavily database driven so we create most objects dynamically including configuring those objects.

The attached example is an update the previous one that uses custom objects and the page configured dynamically.

The issue I'm running into is that when I attempt to edit a WebCombo object, upon loading its data, it's refreshing the entire page and I'm not sure where I'm going wrong.  I was hoping you can offer some assistance in this.

Please make sure to always use Visual Studio 2008 when working with us since that's the environment we're still using for the time eing.  Thank you.

[EDIT] Updated attachment to most recent version.