VC#2005 will have edit & continue
-
Judah Himango wrote: Visual C# 2005 will have edit and continue. Woohoo. I never found it very useful in C++, and I doubt I'll find it useful with C#. Maybe 1 time out of a 100, while in the debugger, I'll say "gee, I wish I could change that line". And when I used it in C++, it had some wierd side-effects, causing me to think perfectly good code was broken. Marc MyXaml Advanced Unit Testing
Yep, about the same for me. I have used it a couple times when I am lazy and have tracked down through a bunch of code and do not want to go through all those steps again. For the most part though, it is not that important to me. Rocky <>< www.HintsAndTips.com - Now with "Recommendation" postings www.MyQuickPoll.com - Now with Recent Poll List www.GotTheAnswerToSpam.com - Again :)
-
I too have found it to be useless. If I find an error, I fix it and restart. Editing and continuing is just wrong as the program may not be in the same state as it should be the next time you run it from the beginning. -- Wir müssen leben bis wir sterben.
It's a judgment call really. Sometimes it's ok; sometimes it's not. As for me, I'm all about E&C when it's appropriate. Jeremy Falcon
-
Well, if it means anything, 90% of the time if something weird happens, I do a clean rebuild before debugging any further... and it frequently solves the problem.. :rolleyes: An expert is somebody who learns more and more about less and less, until he knows absolutely everything about nothing.
-
Hopefully not a repost, just saw that friday some MSDN blogs reported that Visual C# 2005 will have edit and continue. Wooo! This will certainly be a big productivity enhancer IMO. Any remotely useful information on
Oh man, can't wait for that! Now it's: 1. Modify code-behind file(s) of ASP.NET project. 2. Build. 3. Run in Debugger (F5) 4. Wait 83 seconds! (I just timed it.) 5. Repeat. The startup time is insane, and I have a fast box too: P4 2.8Ghz, 1.5GB RAM. Regards, Alvaro
Our enemies are innovative and resourceful, and so are we. They never stop thinking about new ways to harm our country and our people, and neither do we. - George W. Bush
-
Oh man, can't wait for that! Now it's: 1. Modify code-behind file(s) of ASP.NET project. 2. Build. 3. Run in Debugger (F5) 4. Wait 83 seconds! (I just timed it.) 5. Repeat. The startup time is insane, and I have a fast box too: P4 2.8Ghz, 1.5GB RAM. Regards, Alvaro
Our enemies are innovative and resourceful, and so are we. They never stop thinking about new ways to harm our country and our people, and neither do we. - George W. Bush
Alvaro Mendez wrote: 4. Wait 83 seconds! (I just timed it.) Let me save you some time. First, stop IIS (iisreset /stop) Go to C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files. Now, delete every entry under the name of your virtual directory (those pesky random-named '3af003a7' directories). If you don't feel like deleting things, just move them to another directory. They're just temporary, anyways. start IIS again. (iisreset /start) Now, it'll take only a few seconds (3~5) to start your ASP.NET solution. I have a batch file scheduled to run this at midnight. Yes, even I am blogging now!
-
Hopefully not a repost, just saw that friday some MSDN blogs reported that Visual C# 2005 will have edit and continue. Wooo! This will certainly be a big productivity enhancer IMO. Any remotely useful information on
I think E&C is great. Sure, it won't help solve any application design issues, but having to rebuild the entire app because my chubby fingers typed something like "InsertVendot" instead of "InsertVendor" gets old quickly. I just don't understand the folks who claim E&C is useless. I don't require something to be useful in every situation before I put it in my tool box. Anything that saves me some time while debugging is a welcome addition. Charlie if(!curlies){ return; }
-
Judah Himango wrote: Visual C# 2005 will have edit and continue. Woohoo. I never found it very useful in C++, and I doubt I'll find it useful with C#. Maybe 1 time out of a 100, while in the debugger, I'll say "gee, I wish I could change that line". And when I used it in C++, it had some wierd side-effects, causing me to think perfectly good code was broken. Marc MyXaml Advanced Unit Testing
LOL. I thought I was the only one that thought that way! I never use it in C++ either. Cheers, Tom Archer "Use what talents you possess. The woods would be very silent if no birds sang there except those that sang best." - William Blake * Inside C# -Second Edition * Visual C++.NET Bible * Extending MFC Applications with the .NET Framework
-
Alvaro Mendez wrote: 4. Wait 83 seconds! (I just timed it.) Let me save you some time. First, stop IIS (iisreset /stop) Go to C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files. Now, delete every entry under the name of your virtual directory (those pesky random-named '3af003a7' directories). If you don't feel like deleting things, just move them to another directory. They're just temporary, anyways. start IIS again. (iisreset /start) Now, it'll take only a few seconds (3~5) to start your ASP.NET solution. I have a batch file scheduled to run this at midnight. Yes, even I am blogging now!
Wow, thanks for the great tip! I'll try it tomorrow. Can you point me to a link that explains this behavior (temporary files and why they affect startup time)? Thanks again, Alvaro
Our enemies are innovative and resourceful, and so are we. They never stop thinking about new ways to harm our country and our people, and neither do we. - George W. Bush
-
Judah Himango wrote: Visual C# 2005 will have edit and continue. Woohoo. I never found it very useful in C++, and I doubt I'll find it useful with C#. Maybe 1 time out of a 100, while in the debugger, I'll say "gee, I wish I could change that line". And when I used it in C++, it had some wierd side-effects, causing me to think perfectly good code was broken. Marc MyXaml Advanced Unit Testing
It worked a lot better in VB - not that I'm trying to compare C# and VB ;P Stuart Dootson 'Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p'
-
Wow, thanks for the great tip! I'll try it tomorrow. Can you point me to a link that explains this behavior (temporary files and why they affect startup time)? Thanks again, Alvaro
Our enemies are innovative and resourceful, and so are we. They never stop thinking about new ways to harm our country and our people, and neither do we. - George W. Bush
Alvaro Mendez wrote: Can you point me to a link that explains this behavior (temporary files and why they affect startup time)? Sorry, I can't. Someone at the Lounge explained me this a while ago and didn't provide it also. I think it's more of a VS.NET bug. I have a friend using VS.NET 2005 and it doesn't seem to have this bug. Please, let me know if it worked. Yes, even I am blogging now!
-
It worked a lot better in VB - not that I'm trying to compare C# and VB ;P Stuart Dootson 'Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p'
Stuart Dootson wrote: It worked a lot better in VB Yes, but I don't work better in VB. :-D Marc MyXaml Advanced Unit Testing
-
Stuart Dootson wrote: It worked a lot better in VB Yes, but I don't work better in VB. :-D Marc MyXaml Advanced Unit Testing
Same here - my only real experience of VB (and Edit 'n' Continue!) is VBA in Excel spreadsheets - the classic 'little application that grew and grew'....It could do with being refactored but I can only take VB for an hour at a time, so that isn't going to happen!!! Stuart Dootson 'Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p'
-
Alvaro Mendez wrote: Can you point me to a link that explains this behavior (temporary files and why they affect startup time)? Sorry, I can't. Someone at the Lounge explained me this a while ago and didn't provide it also. I think it's more of a VS.NET bug. I have a friend using VS.NET 2005 and it doesn't seem to have this bug. Please, let me know if it worked. Yes, even I am blogging now!
It didn't work. It's still taking 83 seconds. Temporary files don't seem to be the problem. :-( Regards, Alvaro
Our enemies are innovative and resourceful, and so are we. They never stop thinking about new ways to harm our country and our people, and neither do we. - George W. Bush
-
Alvaro Mendez wrote: 4. Wait 83 seconds! (I just timed it.) Let me save you some time. First, stop IIS (iisreset /stop) Go to C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files. Now, delete every entry under the name of your virtual directory (those pesky random-named '3af003a7' directories). If you don't feel like deleting things, just move them to another directory. They're just temporary, anyways. start IIS again. (iisreset /start) Now, it'll take only a few seconds (3~5) to start your ASP.NET solution. I have a batch file scheduled to run this at midnight. Yes, even I am blogging now!
I have been having this problem on 1 machine also. I have several others that work fine. Don't know what it is, but I'll try your tip tonight. Hope it works. Thanks for that! If it does work, I'll try to figure out why I get the temp files on 1 machine and not others and post back.