BrighterLater
Board Regular
- Joined
- Sep 16, 2005
- Messages
- 114
Because all the VBA modules, class and form code are bundled in projects. I find that this makes it difficult to compare two versions of any code components.
The Addin project I am working on has 40 modules, 40 class modules and 25 forms (700 procedures in all, in a 4 Meg xls file). I find it difficult to maintain a development version of my code, in parallel to making fixes on older versions being used in production, and keep my modifications in synch.
What do people use on larger projects? (There's only me, so locking stuff to other team members isn't an issue.)
What I thought I might do was to write a bit of code that, for each release, exported all the application components to a release folder.
I then thought I might use Apache Subversion to store these release folders and their files. This would enable me to compare textbase files, and for the graphical part of forms at least I'd know which were different.
But that all sounds a bit complicated; doesn't it? Is there a simpler way?
(I was going in that direction because in another part of my work I have a client server project: IDL client (which uses Eclipse as the DE and incorporates Subversion), and C++ Server using Eclipse/Subversion as the DE.)
I would welcome any comments. I am also aware that people can be very attached to their way of working so please can we enjoy any diversity of opinions and experience that might emerge; the last thing I want to do is to waste people's time in a heated debate.
Thanks - Mike
The Addin project I am working on has 40 modules, 40 class modules and 25 forms (700 procedures in all, in a 4 Meg xls file). I find it difficult to maintain a development version of my code, in parallel to making fixes on older versions being used in production, and keep my modifications in synch.
What do people use on larger projects? (There's only me, so locking stuff to other team members isn't an issue.)
What I thought I might do was to write a bit of code that, for each release, exported all the application components to a release folder.
Code:
application.VBE.ActiveVBProject.VBComponentsBut that all sounds a bit complicated; doesn't it? Is there a simpler way?
(I was going in that direction because in another part of my work I have a client server project: IDL client (which uses Eclipse as the DE and incorporates Subversion), and C++ Server using Eclipse/Subversion as the DE.)
I would welcome any comments. I am also aware that people can be very attached to their way of working so please can we enjoy any diversity of opinions and experience that might emerge; the last thing I want to do is to waste people's time in a heated debate.
Thanks - Mike
