HighTechTalks DotNet Forums  

RE: Upgrading from VS 6 to VS .NET 2003 with version control

Visual Studio.net (VSS) microsoft.public.vsnet.vss


Discuss RE: Upgrading from VS 6 to VS .NET 2003 with version control in the Visual Studio.net (VSS) forum.



Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old   
AT
 
Posts: n/a

Default RE: Upgrading from VS 6 to VS .NET 2003 with version control - 08-06-2003 , 04:34 AM






Hi Ken,

I am not sure about your projects' architecture.

In a general, I think that you want to convert VS6.0 Workspace/Projects to
VS.NET 2003 Solution/Projects. Although VSS can be intergrated smoothly
with VS IDE, they are different products. My suggestion is:

1. Get the VS6.0 Workspace/Projects from VSS.

2. Open VS6.0 Workspace/Projects in VS.NET 2003 to convert them to VS.NET
2003 Solution/Projects.

3. Add VS.NET 2003 Solution/Projects to VSS.

If I have misunderstood your concern, please let me know.

In addtion, I don¡¯t think there is documentation on the
SccProjectFilePathRelativizedFromConnectionX fields in the solution file
and the PROJECT_FILE_RELATIVE_PATH/SOURCE_CONTROL_SETTINGS_PROVIDER fields
in the project vssscc files. I strongly advise against modifying the hint
files manually. These files should be kept in sync with the
project/solution file (since scc settings are also persisted there), and
also with the mssccprj.scc file possible generated by the source control
provider.

Best regards,

Jacob Yang
Microsoft Online Partner Support
<MCSD>
Get Secure! ¨C www.microsoft.com/security
This posting is provided ¡°as is¡± with no warranties and confers no rights.


Reply With Quote
  #2  
Old   
senthil
 
Posts: n/a

Default RE: Upgrading from VS 6 to VS .NET 2003 with version control - 08-25-2003 , 05:13 PM






Hi,
Is it possible to write a program or macro or by using
automation interface to convert hundreds of VC 7 solution
files to visual studio 2003 solution files.

Thanks
senthil

Quote:
-----Original Message-----
Hi Ken,

I am not sure about your projects' architecture.

In a general, I think that you want to convert VS6.0
Workspace/Projects to
VS.NET 2003 Solution/Projects. Although VSS can be
intergrated smoothly
with VS IDE, they are different products. My suggestion
is:

1. Get the VS6.0 Workspace/Projects from VSS.

2. Open VS6.0 Workspace/Projects in VS.NET 2003 to
convert them to VS.NET
2003 Solution/Projects.

3. Add VS.NET 2003 Solution/Projects to VSS.

If I have misunderstood your concern, please let me
know.

In addtion, I don¡¯t think there is documentation on the
SccProjectFilePathRelativizedFromConnectionX fields in
the solution file
and the
PROJECT_FILE_RELATIVE_PATH/SOURCE_CONTROL_SETTINGS_PROVIDE
R fields
Quote:
in the project vssscc files. I strongly advise against
modifying the hint
files manually. These files should be kept in sync with
the
project/solution file (since scc settings are also
persisted there), and
also with the mssccprj.scc file possible generated by
the source control
provider.

Best regards,

Jacob Yang
Microsoft Online Partner Support
MCSD
Get Secure! ¨C www.microsoft.com/security
This posting is provided ¡°as is¡± with no warranties
and confers no rights.

.


Reply With Quote
  #3  
Old   
jim
 
Posts: n/a

Default RE: Upgrading from VS 6 to VS .NET 2003 with version control - 08-26-2003 , 10:23 AM




Anything is possible.

Quote:
-----Original Message-----
Hi,
Is it possible to write a program or macro or by using
automation interface to convert hundreds of VC 7
solution
files to visual studio 2003 solution files.

Thanks
senthil

-----Original Message-----
Hi Ken,

I am not sure about your projects' architecture.

In a general, I think that you want to convert VS6.0
Workspace/Projects to
VS.NET 2003 Solution/Projects. Although VSS can be
intergrated smoothly
with VS IDE, they are different products. My
suggestion
is:

1. Get the VS6.0 Workspace/Projects from VSS.

2. Open VS6.0 Workspace/Projects in VS.NET 2003 to
convert them to VS.NET
2003 Solution/Projects.

3. Add VS.NET 2003 Solution/Projects to VSS.

If I have misunderstood your concern, please let me
know.

In addtion, I don¡¯t think there is documentation on
the
SccProjectFilePathRelativizedFromConnectionX fields in
the solution file
and the
PROJECT_FILE_RELATIVE_PATH/SOURCE_CONTROL_SETTINGS_PROVID
E
R fields
in the project vssscc files. I strongly advise against
modifying the hint
files manually. These files should be kept in sync with
the
project/solution file (since scc settings are also
persisted there), and
also with the mssccprj.scc file possible generated by
the source control
provider.

Best regards,

Jacob Yang
Microsoft Online Partner Support
MCSD
Get Secure! ¨C www.microsoft.com/security
This posting is provided ¡°as is¡± with no warranties
and confers no rights.

.

.


Reply With Quote
Reply




Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.