By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,962 Members | 1,791 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,962 IT Pros & Developers. It's quick & easy.

My Pretty Listing is going haywire...

P: n/a
I've got a serious problem. I've got Visual Studio 2005 installed, and of
course I'm using the Pretty Listing formatting function. When I start up VS,
everything is fine, but after a while (which can be one minute or one hour)
the Pretty Listing starts acting weird. For instance, if I start writing
"for...", it changes it to f(o) r" or something like that.

When that starts happening, I can't code at all and have to restart VS.
Sometimes that helps - some times I have to do it more than once.

If I turn off Pretty Listing in the VS Options, I can code normally, but
then of course I don't benefit from all the nice fringe benefits of using
Pretty Listing. So I don't want to keep it turned off.

What the heck can I do - is this a bug? It started after I installed the
latest SP (1) for VS 2005. I've never had the problem before. I cannot say
for sure that it has to do with the SP, but chances are that it does...

Anybody else have the same experience?

Cheers,
Johnny J.
May 22 '07 #1
Share this Question
Share on Google+
3 Replies


P: n/a
I have the same problem and cannot figure out what is going on. Often, after I compile, the pretty listing just freaks out and does exactly what you described.

D(im)
F(o)r

Every keypress results in an hourglass as if a search for something is constantly going on.

You are not alone! If anyone knows how to fix this please reply!
May 24 '07 #2

P: n/a
I just found a work around for this problem that tentatively seems to work. After I compile, the file that I am working in begins to act up with the crazy formatting.

If I click the [Design] view of the form and then click back to the form's code view this seems to fix the problem (at least until the next compile). The crazy formatting stops.

May 24 '07 #3

P: n/a
OK - I did some investigating and came up with the following:

http://support.microsoft.com/default.aspx/kb/916209
As far as I understand from what I've read in different forum postings, the
problem exists in different "flavours":

1) Parantheses are added when autosave kicks in and makes the code window
lose focus. This is relatively harmless because it doesn't happen a lot
(depending on your autosave settings of course)

2) The problem I had: You're sitting there typing code, and suddenly it
starts adding parantheses that can't be deleted.

3) The problem Markosoft had (I don't know for sure if it's the same as #2
or if it has to do with the compiling).
As you see from the above KB article, there's a Hotfix available from
Microsoft. Unfortunately it's not so easy getting hold of. Microsoft seems
reluctant to release it and wants complete control over who gets it.

I had to actually call the MS support here in Sweden where I live. They put
me in contact with a Support team in Finland. They couldn't send me the fix,
but put in a request to the MS developers that I should have the Hotfix.
After a short while, I got a mail from a guy from the Microsoft Visual
Studio technical support team with a link to a password protected file
containing the Hotfix. He even tried calling me personally to verify that I
really needed the fix and that it actually solved the problem.

However, I installed it and so far it seems to have solved the problem. I
cannot say for sure, though, because it only happened when I had been coding
for a long while. But I haven't had the problem since the fix was installed,
anyway.

Cheers,
Johnny J.


<markosoftskrev i meddelandet
news:%2****************@TK2MSFTNGP02.phx.gbl...
>I have the same problem and cannot figure out what is going on. Often,
after I compile, the pretty listing just freaks out and does exactly what
you described.

D(im)
F(o)r

Every keypress results in an hourglass as if a search for something is
constantly going on.

You are not alone! If anyone knows how to fix this please reply!

May 25 '07 #4

This discussion thread is closed

Replies have been disabled for this discussion.