Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Apr 21, 2009 07:41 AM by VeganMan
Apr 14, 2009 10:29 PM|LINK
It's clear that behind the scenes that MS is building a structure of some sort to represent the aspx page. I'm going round and round fixing perfectly formatted source code that's in the wrong place. Time and time again.
"No that cell used to contain 'Fax:' having now dropped in <asp:Textbox blah blah> upsets the control generation because now the same ID is used twice."
Sure it's like a 6K long aspx file, and sure I'm getting caught in the <change><wait><change><wait> loop, but the wait loop is already a known problem.
Or am I being singled out for punishment by the computer gods?
Apr 15, 2009 03:45 AM|LINK
I haven't seen this. Are you running VS2k8 sp1?
Apr 15, 2009 03:53 PM|LINK
Yea all the latest patches etc etc.
Thinking about it, I occasionally run across 'System Exception Error: No more memory'. And because it looks like a soft landing I probably save my work, then exit /re-enter VS. (Yea I know - probably not my most brilliant practice huh?)
Easy enough to speculate that VS is smart enough to detect the lack of available memory - to make it a VS exception and not a Windows thing, but isn't smart enough to roll-back the transaction it was doing on the behind-the-scenes datastructure.
Maybe the memory upgrade (2G to 4G) - and the clever things to do in order to get the most out of the 4G - will help.
Apr 21, 2009 07:41 AM|LINK
VS does strange things to my code. I could be working on a formview in the edittemplate, then I see a bunch of <p></p> tags in a row for no appearent reason. Once I had to remove about 15 occurances of then. What the.... is it just me???