Now I've done it...

J

Johnny J.

I wanted to exchange all the ComboBoxes in my project with a special
MyComboBox inherited from the Regular combobox but with a little extra code.

Because I didn't want to remove all the normal comboboxes and drag and drop
MyComboBoxes, I did a find and replace in my entire solution which consists
of 13 projects and a lot of different forms and replaced
"System.Windows.Forms.ComboBox" with "UserControls.MyComboBox" (or whatever
my combobox is called...) everywhere, including the designer files of
course.

That went ok up to 99%. Most of my forms showed that the standard comboboxes
were now indeed MyComboBox'es.

But ONE form out of them all refuse to show in the designer. I get the
cryptic pink errormessage with a lot of errors basically saying that som
error occured when trying to deserialize the form.

If I RUN the program, however, the form shows nicely and all the comboboxes
are MyComboBox'es (as they should be).

Now how can I get the designtime designer to show the form again. Is there
any way of "re-serializing" it or?

OF COURSE it was the most important form of them all!!! We do have source
control, but if I revert the changes, I'll back to zero. And all the other
changes work fine... just this one form.

Cheers,
Johnny "Clutz" J.
 
J

Johnny J.

Never mind, I solved the problem.

It is a long story and quite complicated to explain, so I won't bore you
with that...

Cheers,
Johnny J.
 
P

Peter Duniho

Johnny said:
Never mind, I solved the problem.

It is a long story and quite complicated to explain, so I won't bore you
with that...

Yes, of course. After all, we definitely don't want to see any
explanations of how to fix things in this newsgroup. Especially if they
are complicated things that would be more difficult for someone else to
figure out on their own.

We also hate to have subject lines that actually describe the problem.
It's much better to write something vague and irrelevant such as "Now
I've done it" or similar, so that you have to read through the entire
post before you have some idea of the general problem being asked about.

No, wait. I'm sorry. I have that all mixed up. All of the above is
the opposite of the reality.

Please consider adjusting your use of this newsgroup so that your posts'
subjects are more usable, and so that you still share solutions with
others. If your question was worth asking here, it's worth answering
here, even if you answer it yourself. Conversely, if it's not worth
answering here, you shouldn't have asked it in the first place.

Thanks,
Pete
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top