Windows Form Designer option to give me the VS2003 method?

[active]

With VS2005 the windows form designer uses the files *.Designer.vb

I hope no one at MS is reading this because I know it will upset them to
know - I like the old way better!

I've been looking at the Options available for the Windows Form Designer and
do not see one that would give me the older method.

Is there such an option?


Thanks

 

[RobinS]

No, there's not. You'll get used to it. ;-)

Robin S.

 

[active]

But will I learn to like it?

thanks

No, there's not. You'll get used to it. ;-)

Robin S.

 

[RobinS]

I can't say; it's an attitudinal thing. ;-)

You can choose to be annoyed by it every time you open a form, or you can
decide you like not having to sift through the designer-generated code all
the time because you can't change it anyway, and now you can concentrate on
your own code.

I like it (for the aforementioned reason), but change in any form is
frequently annoying, no matter what it is.

Robin S.
-----------------------------

 

[lord.zoltar]

With VS2005 the windows form designer uses the files *.Designer.vb

I hope no one at MS is reading this because I know it will upset them to
know - I like the old way better!

I've been looking at the Options available for the Windows Form Designer and
do not see one that would give me the older method.

Is there such an option?

Thanks

I don't think it's possible. I actually quite hated the VS2003 style.
You're the first person I know who says they liked it more!
I didn't use VS2003 much, but having all the generated code in the
same file really bothered me. The computer I was using was a little
slow... sometimes I'd be typing, selecting, cutting, copying, pasting
- all a bit too fast, and if the IDE didn't keep up with me, there
were a couple of times I lost the piles of code at the top of the
file. That would also usually cause the IDE to crash on me if the form
designer was also open (because I just deleted all the code it used!).
This led to a couple instances of recreating large forms from
scratch.
I like the new way much better, and it's how I normally structure
programs in other languages; UI set up code in a seperate file
whenever possible.

 

[active]

I don't believe one can 'choose to be annoyed" or choose to not be annoyed.
You either are or aren't - no control.

So I glad it does not annoy me - it's a small thing but I thought I'd ask -
just in case.

Hey, I love VS. Always have.

 

[active]

Who know: not just the first person you know that likes it, maybe the only
one in existence.
I'll never admit it again.

Really the only thing I liked about it was that I could save an entire form
as sample code in one file and retrieve it later. There are many examples of
code on the internet that give the entire sample in one form that one can
paste into a form (one file) and run.


Thanks for the reply

 

[lord.zoltar]

Really the only thing I liked about it was that I could save an entire form
as sample code in one file and retrieve it later. There are many examples of
code on the internet that give the entire sample in one form that one can
paste into a form (one file) and run.

Thanks for the reply

Hmm yeah i can see how that would be useful. I suppose you could still
do that in VS2005 (all the UI setup) manually, but then the Form
Designer might not be able to handle it... actually, what would happen
if you opened a VS2003 file in VS2005? I've never tried. how does the
Form Designer handle that?

 

[CodeMonkey]

Hmm yeah i can see how that would be useful. I suppose you could still
do that in VS2005 (all the UI setup) manually, but then the Form
Designer might not be able to handle it... actually, what would happen
if you opened a VS2003 file in VS2005? I've never tried. how does the
Form Designer handle that?

From what I recall, when I upgraded a 2003 project to 2005, the
designer code stayed in the same file as the form code.

The designer.vb file is nothing more than a partial class... I'm sure
the designer just uses which ever it finds.

 

[Herfried K. Wagner [MVP]]

I don't think it's possible. I actually quite hated the VS2003 style.
You're the first person I know who says they liked it more!

I like the idea of separating designer-generated code from user-generated
code, but I hate those cases in which it's necessary to modify the
designer-generated code in order to make something work.

 

[active]

Right, I have a solution with old and new forms. The old ones are still one
file.

 

[RobinS]

active,

I'm not going to go all metaphysical on you here, but your feelings are
generally created by your thoughts. So if every time you open the code
behind a form, you think "#@!!&^#!!" you will feel annoyed. If every time
you open the code behind a form, you think, "How clean and organized this
looks!", you will feel content. ;-)

Robin S.
Ts'i mahnu uterna ot twan ot geifur hingts uto.
-----------------------------------------------

 

[active]

OK

thanks

active,

I'm not going to go all metaphysical on you here, but your feelings are
generally created by your thoughts. So if every time you open the code
behind a form, you think "#@!!&^#!!" you will feel annoyed. If every time
you open the code behind a form, you think, "How clean and organized this
looks!", you will feel content. ;-)

Robin S.
Ts'i mahnu uterna ot twan ot geifur hingts uto.

 

[Darin]

I agree w/ both sides - it does make the code cleaner, but it is a PAIN
when you have to modify the designer code. It would have been nice if VS
had an option under the View menu that was Designer Code or something
like that.

Darin