4 ms·
Woah, woah, you're saying edit and continue, which everyone's flipping out about in Light Table, isn't that much of an improvement? I think the problem is more
by mattmanser 14y ago
Woah, woah, you're saying edit and continue, which everyone's flipping out about in Light Table, isn't that much of an improvement?
I think the problem is more that most people don't know it exists and it's almost impossible to get Edit and Continue working properly in Visual Studio. I think I've only ever managed once for console programs, but then it completely breaks debugging for ASP.net.
There's a load of things I wish worked properly in Visual Studio that don't that I know would make a massive difference in my productivity. It's almost impossible to drop into .Net library code, load external symbols, etc. When you get a gnarly problem where it's due to some 'helpful' utterly insane choice that the ASP.Net framework guys made the time I would save just dropping into the code from the IDE is massive, rather than popping open ILSpy, figuring out the flow and trying to figure out the path the program is taking.
My workflow is code, read through the code, test the code, fix the code, test the code, fix the code. Annoyingly during testing I can't edit the damn code to fix the simple mistakes I've missed. Edit and continue would be great if it actually worked.
- seanmcdirmid 14y agoLight Table goes way beyond "edit and continue," which is small potatoes left over from Smalltalk (and early systems that support hot code swapping). Light Table supports much more feedback (we call it live programming), the code is actually re-evaluated when changed; edit and continue only holds for future, not previous execution, which is why it breaks so easily.
- meaty 14y ago+1 for edit and continue not working. It rarely does what it says on the tin. Usually in our case as we have 64-bit COM binary dependencies, we can't use it anyway as it doesn't work in 64-bit CLR processes. In 32-bit processes it throws the HRESULT of death MsgBox and dies. Regarding ASP.Net debugging, I have to resort to the same thing. We actually have a set of custom framework assemblies as a last resort debugging tool that we load into the GAC in a VMware instance which have gone through a tool I wrote using Mono.Cecil that makes all members and classes public and not sealed. They all have exported PDBs as well from MS symbol server so we can step through :) However, Visual Studio would get a fuck ton more love from me if it didn't crash 8 times a day as well. It's so damn unreliable. My "other world" of gcc + C + vim + Linux is far more pleasant.
- MichaelGG 14y agoLight Table looks like a REPL on steroids, E-n-C is like REPL on tranquilizers. It has limited use, allowing only limited changes. There's little interactive environment (immediate window), and even that's pretty limited. So no, I don't think edit and continue is that big of a deal. A REPL would have been easier and more useful, see F# Interactive. As far as stepping into code, I find the MS symbol server and .NET source code stepping to "just work". But I sympathize with the pain of debugging a deep stack in ASP.NET, trying to figure out how their abstraction worked. For 3rd party libraries, would it not be up to that publisher to publish their own symbols/source?