VS 2008 Edit and Continue broken

  • Thread starter Thread starter Lloyd Sheen
  • Start date Start date
L

Lloyd Sheen

Title says it all. I have reinstalled this "terrible" version of VS now 4
times and I am having trouble with why MS released this.

I do a simple one line addition and it tells me thing are not sync'ed. Well
sync them IDE.

MS are you there??????

LS
 
How about actually describing what you want to do and how you are attempting
to do it and what you are getting for a response instead of just ranting?
 
Scott M. said:
How about actually describing what you want to do and how you are
attempting to do it and what you are getting for a response instead of
just ranting?
Click to expand...

Ok I inserted the following lines (new) into an executing procedure.

Dim toFolderName As String
toFolderName = Path.Combine(toFolder.FolderName,
Path.GetFileName(folderName))


This made the code in the procedure:

Dim toFolder As FolderInfo = CType(foldersListBox.SelectedItem,
FolderInfo)
Dim fromFolder As String = folderName
Dim toFolderName As String
toFolderName = Path.Combine(toFolder.FolderName,
Path.GetFileName(folderName))

FileSystem.MoveDirectory(fromFolder, toFolderName)
Me.DialogResult = Windows.Forms.DialogResult.OK
Close()


Now when I attempted to set the executing line to the first line ( one time
I noticed in the watch window that toFolder was nothing after a change) I
get a first message that I cannot set the execution to that line. When I
get that I do not want to execute the sub any further so I attempted to set
the executing line to setting the dialogresult. This resulted in the error
and I had to shut down VS 2008.

LS
 
I've given up on Edit-and-Continue in VB.NET. I now restart every time I make
a change.

Pity, it was one of the great features of MS BASIC going back to QuickBasic.

I don't know enough about the plumbing of .NET but I suspect that now
programs are all JIT Compiled, rather than interpreted, it is too hard to
implement properly.

All I know is Edit-And-Continue makes the IDE unreliable, so I don't use it.
Even Stop-and-continue can be a problem if you use third party or COM objects
- viewing a property can execute code underneath, I suppose.
 
SurturZ said:
I've given up on Edit-and-Continue in VB.NET. I now restart every time I
make
a change.

Pity, it was one of the great features of MS BASIC going back to
QuickBasic.

I don't know enough about the plumbing of .NET but I suspect that now
programs are all JIT Compiled, rather than interpreted, it is too hard to
implement properly.

All I know is Edit-And-Continue makes the IDE unreliable, so I don't use
it.
Even Stop-and-continue can be a problem if you use third party or COM
objects
- viewing a property can execute code underneath, I suppose.
Click to expand...

Under VS 2005 I never had a problem. One thing I think causes a problem in
VS 2008 is Linq. I know you cannot edit linq statements and I have many in
my code.

LS
 
Sure sorry your having so much trouble...  But, I have had zero problems with
VS2008.  Maybe it's VB thing though, because I mostly work in C#.
Click to expand...

Doesn't seem to be a VB thing, I work almost exclusively in VB now,
and most of the developers I work with are doing 95% VB. I don't know
of any problems from the other guys and I haven't had a single problem
since 2008 was released. I am however running Team Suite so perhaps a
version difference is to blame?

Thanks,

Seth Rowe [MVP]
http://sethrowe.blogspot.com/
 
Doesn't seem to be a VB thing, I work almost exclusively in VB now,
and most of the developers I work with are doing 95% VB. I don't know
of any problems from the other guys and I haven't had a single problem
since 2008 was released. I am however running Team Suite so perhaps a
version difference is to blame?

Thanks,

Seth Rowe [MVP]http://sethrowe.blogspot.com/
Click to expand...

LOL

Apparently I just jinxed myself. I just received my first crash in
Visual Studio 2008. When using Ctrl+M+L to expand my code file the
Visual Basic Compiler went kaboom.

That'll teach me to say I haven't had any problems! :-)

Thanks,

Seth Rowe [MVP]
http://sethrowe.blogspot.com/
 
terrible? Wow haven't used VS2005 much have you? Haven't had a single
problem with 2008 yet... 2005 was almost unbarable to use at times...
 
Smokey Grindel said:
terrible? Wow haven't used VS2005 much have you? Haven't had a single
problem with 2008 yet... 2005 was almost unbarable to use at times...
Click to expand...

Used VS 2005 for about 3 years without a hickup.

LS
 
Back
Top