vc7 to vc8 and back to vc7

vc8 converts vc7 files, but vc7 will not read vc8 files after conversion and
vc8 leaves nothing behind for vc7 (same file names used). So, what is a
person supposed to do when thier employer liscensed vc 7 at work and they
have vc8 at home?

I really don't see any logic in buying vc7 just to work on the same solution
and projects I did at work, from home, when I already own 2005 professional.

Bruno
Sat Oct 21 01:58:16 CDT 2006

> vc8 converts vc7 files, but vc7 will not read vc8 files after conversion
> and vc8 leaves nothing behind for vc7 (same file names used). So, what is
> a person supposed to do when thier employer liscensed vc 7 at work and
> they have vc8 at home?

Hi,
Create a copy of the VC2003 sln and proj files, then convert the originals
to VC2005.
At work you open the VC2003 solution. At home the VC2005 solution.

--

Kind regards,
Bruno van Dooren
bruno_nos_pam_van_dooren@hotmail.com
Remove only "_nos_pam"

David
Sat Oct 21 03:41:16 CDT 2006

>Create a copy of the VC2003 sln and proj files, then convert the originals
>to VC2005.
>At work you open the VC2003 solution. At home the VC2005 solution.

And you have to maintain them both.

Alternatively, when you go home, have a break from work. :)

Dave

Bruno
Sat Oct 21 08:56:23 CDT 2006

> And you have to maintain them both.

Obviously, but project settings do not change that often, and the point of
the VC2005 solution is primarily just to work on the code, I guess.

> Alternatively, when you go home, have a break from work. :)

... says the MVP. But who am I to comment ;-) Pot, kettle, black, ...

--

Kind regards,
Bruno van Dooren
bruno_nos_pam_van_dooren@hotmail.com
Remove only "_nos_pam"

David
Sat Oct 21 10:41:14 CDT 2006

>> Alternatively, when you go home, have a break from work. :)
>
>... says the MVP. But who am I to comment ;-) Pot, kettle, black, ...

I know :)

Dave

Christopher
Sun Oct 22 21:50:16 CDT 2006

Yea, I guess that is what I will have to do in later stages. But right now,
alot of changes are taking place in the solution and project files, as I
flesh out what goes where and links with what and how. It is a huge project
so there are settings galore. There should be less of that type of stuff in
a week or so hopefully and then I can just concentrate on code changes.

If I only program at work, I'll lose all my programming skills. :) Although
my title is "programmer", I am more of a debugger and adminstrator of 2 line
band-aids. At home I have the freedom to do what ever I want without the
interference of policies and restrictions. Sometimes, I'll take my own hobby
projects to work in the name of "research and study", to have something to
do during downtime.


"Bruno van Dooren [MVP VC++]" <bruno_nos_pam_van_dooren@hotmail.com> wrote
in message news:OrfrxiR9GHA.4012@TK2MSFTNGP04.phx.gbl...
>> And you have to maintain them both.
>
> Obviously, but project settings do not change that often, and the point of
> the VC2005 solution is primarily just to work on the code, I guess.
>
>> Alternatively, when you go home, have a break from work. :)
>
> ... says the MVP. But who am I to comment ;-) Pot, kettle, black, ...
>
> --
>
> Kind regards,
> Bruno van Dooren
> bruno_nos_pam_van_dooren@hotmail.com
> Remove only "_nos_pam"
>
>

bruno_nos_pam_van_dooren
Mon Oct 23 04:58:01 CDT 2006


> Yea, I guess that is what I will have to do in later stages. But right now,
> alot of changes are taking place in the solution and project files, as I
> flesh out what goes where and links with what and how. It is a huge project
> so there are settings galore. There should be less of that type of stuff in
> a week or so hopefully and then I can just concentrate on code changes.

Well, there is a hack that could work, but this is of course at your own risk.
Open the project and solution files in a text editor, and change the VS
version to the value for VS2005 or the other way around.
This works for conversion between VS2002 and VS2003, but I have no idea how
compatible VS2005 is with VS2003.

Of course, if you simply create a backup each time you do this, there is no
danger of damaging your 'work' project files.

--
Kind regards,
Bruno.
bruno_nos_pam_van_dooren@hotmail.com
Remove only "_nos_pam"