Double clicking control does not add code to Code Behind

Paul Walton · September 24th, 2009, 05:34 AM

Hi,
I'm working on the 'Working with Server Controls' exercise (p105) and item 8 does not appear to work i.e. double click the button. In fact in the previous exercises I have had to manually open the Code Behind file in order to copy the code in. However, this code is specific to the control so I'm now stumped!
I'm using VWD Express Edition Version 9 with .Net version 3.5 SP1.

Any ideas?

Also, I'm having to use C# as I get a VB error message that language support has not been installed and so Intellisense is not available. Don't whether it is related!

Regards
Paul

Imar · September 24th, 2009, 05:45 AM

Hi Paul,

That's not how it's supposed to be. Sounds like a faulty installation. You can try repairing / reinstalling Visual Web Developer....

And what happens when you create a brand new web site (File | New Web Site), switch to Design View, drag a Button on the page and double click it. Does it work then?

CHeers,

Imar

Paul Walton · September 24th, 2009, 11:27 AM

I think it is the installation as you suggest. I still get the same problem when I start a new web site. Double clicking the button justs takes it back to the source tab with the asp:Button line highlighted.
One other thing I notice is that I cannot change the button id under the properties. As soon as I tab or return off the field value it returns to 'Button1' (the text value works ok though).
Regards
Paul

Imar · September 25th, 2009, 03:19 AM

From what you describe: reinstall it is.... ;-) This doesn't sound right....

Imar

Paul Walton · September 25th, 2009, 06:08 AM

Have now re-installed on another PC and the problems appear to have been fixed. Can't really see anything different in the installation. Only thing I did notice was that the other PC had MSXML 4 where as my laptop has Ver 6. This could be totally unrelated though!
Thanks for the help.
Regards
Paul

Imar · September 25th, 2009, 05:40 PM

Greta; glad it's working.

I wonder if XML has anything to do with it. I've had various versions of MS XML installed on different machines, and never had the problems you're describing.
You could try to repair VWD through the Control Panel and see if that helps...

Cheers,

Imar