Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Languages / Managed C++ / June 2004

Tip: Looking for answers? Try searching our database.

Can't open VC++ 7.1 projects in 7.0

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
MikeG - 01 Jun 2004 12:01 GMT
We have users who are having a problem reading projects written in VC++ 7.1.  Specifically, here is their e-mail describing the problem

Incompatibility -
7.0 will not open a solution built by 7.1. A time consuming work-around is for the person using 7.0 to open the project built in 7.1 as a visual 6.0 workspace (.dsw). However, in doing this all the parameters are lost and both people are then required to visually match parameters. Since both people often aren't available, simple collaboration becomes unpredictable

Apparently, Visual C++/Studio 2003 equates to 7.1.xxxx and 2002 equates to 7.0.xxxx.  Our users have also stated "We have the problem that Microsoft does not sell Visual C++/Visual Studio version 7.0 or version 7.1.  They identify their products simply as Visual C++/Studio.Net 2003.  This replaced Visual C++/Studio 2002.  There is no reference to version 7.0 or version 7.1.  Further, Microsoft doesn't offer any patches or upgrades to either 2002 or 2003.  The only reference to a version 7.1 anything has to do with some templates that are now available.

Anyone aware of any quick workaround for this problem

Appreciate the help

Mike Griffi
Mike.Griffin@xlmcox.com <remove x's
Peter van der Goes - 01 Jun 2004 12:52 GMT
> We have users who are having a problem reading projects written in VC++ 7.1.  Specifically, here is their e-mail describing the problem:
>
> Incompatibility -
> 7.0 will not open a solution built by 7.1. A time consuming work-around is for the person using 7.0 to open the project built in 7.1 as a visual 6.0
workspace (.dsw). However, in doing this all the parameters are lost and
both people are then required to visually match parameters. Since both
people often aren't available, simple collaboration becomes unpredictable.

> Apparently, Visual C++/Studio 2003 equates to 7.1.xxxx and 2002 equates to 7.0.xxxx.  Our users have also stated "We have the problem that Microsoft
does not sell Visual C++/Visual Studio version 7.0 or version 7.1.  They
identify their products simply as Visual C++/Studio.Net 2003.  This replaced
Visual C++/Studio 2002.  There is no reference to version 7.0 or version
7.1.  Further, Microsoft doesn't offer any patches or upgrades to either
2002 or 2003.  The only reference to a version 7.1 anything has to do with
some templates that are now available."

> Anyone aware of any quick workaround for this problem?
>
> Appreciate the help,
>
> Mike Griffin
> Mike.Griffin@xlmcox.com <remove x's>

There is a way to "downgrade" a Visual Studio .NET solution to 2002.

Try this utility at Code Project that will convert a VS.NET 2003 solution
back to VS.NET 2002.

http://www.codeproject.com/macro/vsconvert.asp

Hope this helps.

Signature

Peter [MVP Visual Developer]
Jack of all trades, master of none.

MikeG - 02 Jun 2004 15:26 GMT
Thanks, Peter.  We're checking it out...

Rate this thread:







Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.