Is there a way?

[Zim Babwe]

VS 2005 VB.NET Windows Project

I have a project that has about 14 forms, class objects, user defined
controls, and I would like to make a new copy of the project. For instance,
my project is called Inventory and I would like to create Inventory2.

When I created Inventory2 in VS 2005, I added some the user defined controls
first, did a build, then added the class objects, then the forms. When I
tried to edit one of the forms, I got that red circle with the X in the
center saying that there were problems.

How can I make a duplicate copy of a project with a new name so I don't mess
up the original? I need to make a bunch of changes and If I have to go
back, then I can just go to the original project.

Thanks

 

[RobinS]

I usually just zip mine up with WinZip and stick a date and time in the
file name, then if I completely screw up the version I'm working on, I can
unzip it on top of the one I've messed up.

Also, you don't need to rename the solution, just copy it to a different
folder. Create a new folder. Open the top folder of the old solution, do
Ctrl-A to select all, then Ctrl-C to copy. Go to the new folder you're
created, and do Ctrl-V to paste them. Then open the solution using the
solution file in the new folder.

You can also create a new solution in a new folder, then do Add Existing
Item and go pick the old items. It will copy them from the old location to
the new and add them to your solution.

Robin S.

 

[Zim Babwe]

Thanks for the reply but I did try your suggestion first and I had some
problems with the new solution. I have some User Controls, which caused
problems in the forms that use them. When I created the new project, I
first copied the User Controls, did a build so they would be usable. I then
imported a form which used the User Controls. I had lots of errors
pertaining to the naming of the User Controls. Fixed them in code, but to
do this with 10-15 or more forms, along with the DataSets, DataReaders,
(wizard generated), just caused other problems.

There must be an easier way, but for now, I copied the original solution to
a backup folder. Gave it a name that I could go back to if needed, then
started to modify the solution the way I want to.

Ain't programming fun?

Thanks

 

[RobinS]

Hmmm. That's weird. I would have copied everything before doing any kind of
build on it. At least copying the whole thing works.

Ain't programming fun?

Gee, this isn't even a programming question.

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

 

[Tom Shelton]

VS 2005 VB.NET Windows Project

I have a project that has about 14 forms, class objects, user defined
controls, and I would like to make a new copy of the project. For instance,
my project is called Inventory and I would like to create Inventory2.

When I created Inventory2 in VS 2005, I added some the user defined controls
first, did a build, then added the class objects, then the forms. When I
tried to edit one of the forms, I got that red circle with the X in the
center saying that there were problems.

How can I make a duplicate copy of a project with a new name so I don't mess
up the original? I need to make a bunch of changes and If I have to go
back, then I can just go to the original project.

Thanks

You get source control system. Like Source Safe. If you don't have source
safe, and can't afford it - there are plenty of free ones. Even if you are a
solitary developer working on a single application, having the ability to roll
back, branch, view history, etc on your source is really valuable. Further, I
would suggest that you regularly back up the source safe (or other source
repository) so that if you machine goes down, you can recover.

 

[Jon Skeet [C# MVP]]

You get source control system. Like Source Safe. If you don't have source
safe, and can't afford it - there are plenty of free ones. Even if you are a
solitary developer working on a single application, having the ability to roll
back, branch, view history, etc on your source is really valuable. Further, I
would suggest that you regularly back up the source safe (or other source
repository) so that if you machine goes down, you can recover.

Preferably, use a source control system other than SourceSafe even if
you *can* afford SourceSafe. Friends don't let friends use SourceSafe


I'd personally recommend Subversion - free, and *so* much better than
VSS: http://subversion.tigris.org