On Mon, 13 Feb 2006 12:57:43 +0100, "Cor Ligthert [MVP]"
<no************@planet.nl> wrote:
Can you give us an example in code?
Well if necessary I will, but it's not so much a specific error that
I'm concerned about, more that I don't understand or know how to do
something that's important to me. Can I go back to my original
question?
In the past under VB2003 I've always found it useful to version my
programs. In other words, when I've achieved a development milestone
with a given code version, to freeze that code and begin a new
development stage with a new copy of the code from the previous stage.
To do this, I start a new empty (eg WinForms) project with an
incremented name and with the files saved in a new folder location, eg
MyProject8xx, and with that project open then use 'Add Existing Item'
to import all the .vb files (and only the .vb files) from the previous
version.
This has worked fine in the past within VB2003. But in trying it under
VB2005 I get these various errors apaprently associated with the Form
Designer-generated code. This is true whether or not I try to import
the .vb files from an 'old' VB2003 folder or one that's been opened
under VB2005 and notionally converted.
It seems that there is something external to the .vb files that needs
importing too. (This seems a bit of a backward step or at least
inelegant in that the complete code for the converted file is no
longer contained within eg a form's .vb code. But be that as it
may...)
Is there a better way of versioning my projects under VB2005?
JGD