Copy Visual InterDev project

How can i copy a Visual InterDev project from one computer to another (both work with PWS/Win98) and force the dest project to work with the dest computer name as server?

Gideon
galorAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
TTomConnect With a Mentor Commented:
Gideon:

Don't know if/how accepting a comment as an answer works, so I am posting this as an answer, just to be sure.

Tom
0
 
jedimikeCommented:
I would like to know the same thing.  The best I came up with is to name the two servers the same thing.
0
 
TTomCommented:
Don't understand the question.  What do you mean by working with the dest computer name as server.

The only way I can see a problem is if the original server name is hard coded into the pages in the project.

I must be missing something, so please provide a little more info (or an example).

Tom
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
galorAuthor Commented:
My computer is called "gidon". I create a vip project in InterDev, and select "gidon" as the server. Now i copy all project files to a computer called "tammy" and replace all "gidon" to "tammy" in vip,sln,asp files.
But, when i open the project on computer "tammy" it still try to connect to server "gidon"!
1. What is the reason for that?
2. Where the InterDev keep the list of files included in the project?

Gideon
0
 
TTomCommented:
I believe InterDev keeps a list of the files in the project in the .vic file, but that file seems to be a "machine language" file, and is probably not editable.

However, it seems to me you are going about things wrong in making your new copy.

Two possible options:

1.  Use the "Copy Web" facility in VID to move your files to your new server.

2.  Copy all the CONTENT files in your project to the new server, and create a NEW VID project, pointing to the new server.  That way, VID will create the appropriate files where it needs them, pointing to the right server.

I do not think VID intended people to try to move things around "manually".

HTH,

Tom
0
 
galorAuthor Commented:
Thank you.

Gideon
0
 
TTomCommented:
Does this effectively answer your question?  If so, would you accept my comment as an answer (or ask me to post an answer)?

Tom
0
 
jedimikeCommented:
why did microsoft do this?  I can move files around if I want! hehe
can someone explain to me the need for a solution (.sln)?  I have never encountered the need for it.  What is its purpose?
0
 
TTomCommented:
Why does M$ do anything? <G>

You can move your files wherever you want.  You just can't expect VID to treat them the way YOU want them to be treated.  The problem here comes in trying to do something that VID is not designed to do.  It offers the option to move files wherever you want them to, it just requires that you do it their way.

As far as .sln goes:  solution files offer a way to organize multiple projects in the same workspace.  For instance, I can create a project on my development machine and a second (virtually identical) project on a production machine.  If I place them both in the same solution file, both projects will be available to me at the same time.  However, each is an independent project, which can be opened separately using the .vip file.  Adding and subtracting projects from a .sln file does not (necessarily) affect the existence of a project, and the same project can be included in numerous .sln files.

Helpful?

Tom
0
 
galorAuthor Commented:
TTom, i accept your comment as an answer.

Gideon
0
All Courses

From novice to tech pro — start learning today.