BeforeMoveNext Event Problem

Hi all,

Ive just been messing around with the wizard control and on a page i have a listview.  It is populated and i select one item in the list.

I have then mapped the page_BeforeMoveNext event to validate that an item has been selected, and for some unknown reason, the listview.selecteditems.count == 0 instead of 1.

If i slap a normal button on the page and click it, the count is 1.

Any ideas anyone?

Gleedo

Extra info

I am using the wizard in Visual Studio 2005.

I have put condition breakpoints on the listviews ItemSelectionChanged and SelectedIndexChanged events to break when the count changes and they fire when i change the selected item, but neither fire when clicking the wizard Next button (which you would expect), but im stumped as to why the selectedindex count == 0.

There is also no call stack available other than the point at which the wizard form is invoked.

I have also tried other controls that use the same properties (selecteditems , selectedindices) and they all work.  Its just the ruddy list view.

Now its working!

Created new form, added wizard, listview and code etc and it just started working.

I guess something must have just got a bit cocked somewhere down the line....very odd.

Have you experienced any problems with the wizard control and vs2005? I am considering buying it, but I can see that vs2005 is not a featured dev.environment (yet).

The Wizard Framework control works fine in VS2005.

<BLOCKQUOTE><table width="85%"><tr><td class="txt4"><img src="/CS/Themes/default/images/icon-quote.gif">&nbsp;<strong>Tim Dawson wrote:</strong></td></tr><tr><td class="quoteTable"><table width="100%"><tr><td width="100%" valign="top" class="txt4">The Wizard Framework control works fine in VS2005.</td></tr></table></td></tr></table></BLOCKQUOTE>

Hi, does the wizard framework required Windows Framework 1.1 to be on the target machine or will it work if 2.0 is the only windows framework installed?

It doesn't require any particular version of the .NET framework. As long as .NET is loaded into your process it'll work fine.