VB.NET Bug in Code Formatting

[Lee Ottaway]

I wonder if anyone else has had this problem. Everything in my VB.NET
2003 project has been working wonderfully for months however, suddenly
whenever I delete some code or cut and paste it elsewhere the divider
lines between the various procedures becomes screwed up. The dividers
move into the middle of the procedure code. Once this happens the
auto formatting of the code also disappears. I have to make sure I
key all the capital letters in the right places, and the underlying of
incorrect or invalid code no longer works. Finally, the intellisense
goes as well. At this point I have to close VB.NET and re-open it
again, wherein it will work for a while before mysteriously going into
the same nose dive.

This problem is really starting to get on my nerves because its
happening, not every few hours but every few minutes.

Any ideas????


Lee

 

[Herfried K. Wagner [MVP]]

Lee,

I wonder if anyone else has had this problem. Everything in my VB.NET
2003 project has been working wonderfully for months however, suddenly
whenever I delete some code or cut and paste it elsewhere the divider
lines between the various procedures becomes screwed up. The dividers
move into the middle of the procedure code. Once this happens the
auto formatting of the code also disappears. I have to make sure I
key all the capital letters in the right places, and the underlying of
incorrect or invalid code no longer works. Finally, the intellisense
goes as well. At this point I have to close VB.NET and re-open it
again, wherein it will work for a while before mysteriously going into
the same nose dive.

I never experienced this problem. Which font do you use in VS.NET's
text editor?

 

[Lee Ottaway]

I'm just using the default which I believe is Courier New.

 

[Herfried K. Wagner [MVP]]

I'm just using the default which I believe is Courier New.

Does this occur with every file or just with a specific file?

 

[Lee Ottaway]

I was hoping it would only happen in one of my files (which is now quite
large with a good number of controls), however it seems to be happening
in any of the files I edit.

Nothing like this happened for a number of months, however I recently
downloaded a trial version of DataDynamics ActiveReports for .NET. The
problem might have coincided with installing this, but its hard to say.
No-one else seems to have had this problem with the product and I picked
up the very latest service pack for it, still the problem persists.

 

[Herfried K. Wagner [MVP]]

I was hoping it would only happen in one of my files (which is now quite
large with a good number of controls), however it seems to be happening
in any of the files I edit.

Thank you. So it's impossible for me to repro this behavior.

Nothing like this happened for a number of months, however I recently
downloaded a trial version of DataDynamics ActiveReports for .NET. The
problem might have coincided with installing this, but its hard to say.
No-one else seems to have had this problem with the product and I picked
up the very latest service pack for it, still the problem persists.

Did you uninstall this product? Does the problem persist? Does
DataDynamics provide a support website or support forums? Maybe other
people using this product experienced the same problems.

 

[Wayne Hoover]

Lee is *UNEQUIVOCALLY NOT ALONE IN THIS*. I have the same damn behavior.
No explanation, and no, it can't be reproduced. I just chalk it up to yet
another bug in VS.Net
2003. One of so many bugs. This POS still isn't prime time.

 

[Lee Ottaway]

One thing I now can confirm is that the problem is not related to
ActiveReports. Even a project with all references removed to this
product has the same problem.

I can also say that, even though the formatting is lost in the current
file, if you edit a different one the formatting is OK. In fact I don't
seem to be able to get it to go wrong in simple classes i.e. those
without controls.

I can also confirm when the formatting is lost. I have a form with
several combo boxes on it. I view the form in design view and then
double click one of the combos to add some code. At that point, instead
of taking me to the code screen, the cursor flickers for a moment and
then remains in design view. I then know that the problem has occured.
If I then go to the code screen, or double-click the combo box again the
formatting will be lost and the odd behaviour begins again.

Regards



Lee

 

[Michael B]

I just read the thread and I am having the same problem. Another thread was
started in another group. I would love an answer. Sadly, MSFT wants $99 for
me to call and tell about it. I hope they read these groups because this is
a nasty issue.

My problem began with a cut and paste as well.

Mike

 

[Michael B]

Did you uninstall this product? Does the problem persist? Does

DataDynamics provide a support website or support forums? Maybe other
people using this product experienced the same problems.

It is certainly not an Active Reports issue. I don't have it installed and I
produced the same errors. It is very annoying.

 

[Lee Ottaway]

Michael

Glad to hear there's a number of us out there that have the same
problem. Hopefully one day this will blight one of the Microsoft
programmers and force them to do something about it. It really is quite
a crippling anomally.

Out of interest, are you running any 3rd party controls in the project
that's giving you a problem? I would love to narrow down whether this
is an inherent VB.NET bug, or whether it's related to a bit of bad code
in a separate control.

Regards


Lee

 

[Michael B]

Glad to hear there's a number of us out there that have the same

problem. Hopefully one day this will blight one of the Microsoft
programmers and force them to do something about it. It really is quite
a crippling anomally.

It is totally crippling. I have tried averything. It just stays with the
project. I am very, very angry that I can't call Microsoft about it without
forking over $249. An e-mail is $99. Sure, they reimburse you if it is their
fault, but who determines that?

Out of interest, are you running any 3rd party controls in the project
that's giving you a problem? I would love to narrow down whether this
is an inherent VB.NET bug, or whether it's related to a bit of bad code
in a separate control.

No 3rd party controls. It all started with a cut and paste. It then infected
the whole project. I am quite furious about it. Talk about limiting
production... property statements won't complete, nothing aligns, and I
can't even get an End Function to show up. I want this addressed.