Hi, maybe this isn't the right place to ask this, but I
need to get the answer to this question. I manage student
lab computers at a college and I need to find out how to
install Microsoft Visual studio 6 TOGETHER with visual
Studio .NET on the SAME machine. To date, I'm having
trouble finding out how to accomplish this.

I've spent hours on the internet, hours browsing books,
and hours asking peers.

Is there a CLEAR, SIMPLE, EASY to follow description or
set of written instructions on how to do this anywhere?
Does Microsoft have an article hidden deep within the
bowels of the Technet pages on MSDN that could help me?

I've run into numerous issues. Incompatabilites between
versions of MS Office and studio 6, between MS office and
studio .NET, order of installation issues between windows,
service packs, and studio 6 and studio .NET, etc, etc,
etc,...

I've built and re-built machines and re-imaged WHOLE labs
full of computers trying to get this task done, but I still
am unable to get the two products (Studio 6 and
Studio .NET) to work together without issues.

I find all sorts of article on how to USE studio 6 or how
to USE studio .NET or how to MIGRATE studio 6 applications
and solutions to Studio .NET ones, but I can find hardly
anything on how to INSTALL, CONFIGURE, and get the programs
to work properly together!!!

If anyone has any ideas, please let me know. Yes. Even if
it's just as simple as browsing through a readme file
somewhere on the install cd's that I've missed.

Thanks in advance for any help.

Paul Kattnig
pkattnig (AT) mesastate (DOT) edu

"Paul Kattnig" <pkattnig (AT) mesastate (DOT) edu> wrote

We have Visual Studio .NET 2003 and Visual Studio 6 (Interdev, VB and C++)
installed in two of our classrooms without any serious problems. FWIW, we
also have Office 2000 installed on these PC's as well. We use Windows 2000
SP4.
As the instructor who uses Visual Studio(s), I'm not the person who does the
installs or makes the images, but I do have to test and use the
functionality.
In general, the software has been successfully installed as follows:
OS and service pack(s)
Office 2000
VS 6
VS.NET,
although I have personally installed VS6 after VS.NET in my office without
ill effects.
I don't like to be the bearer of bad news, but as there doesn't seem to be a
general history of what you describe, you'll probably need to post specifics
of the errors/problems you get here (as one suggestion):

microsoft.public.vsnet.setup


--
Peter [MVP Academic]

Hi Paul,

VS 6 and VS .NET were designed to coexist on the same machine. I assume you
are installing to different directories (that's a requirement). Our lab has
them both installed without any issues.

As Peter suggested, if you could provide more specifics maybe it would ring
a bell. My suggestion would be to install in this order:

Clean install of windows.
Apply all service packs as called for in Windows Update.
Install Office
Apply all service packs as called for in Office Update.
Install VS 6.0.
Apply appropriate service packs.
Verify that everything is working fine.
Install VS .NET.
Apply any service packs.

It should work just fine.

bill burrows

"Paul Kattnig" <pkattnig (AT) mesastate (DOT) edu> wrote

Actually, the order you folks give me is one I've already tried and it DOESN'T work in my case. Our system is usin
MS Office XP, NOT MS Office 2000. When I install Office BEFORE Visual Studio 6, the VS6 install breaks the abilit
of Excel XP to do database functions and it also breaks the ability of MS Access XP to either create a new database or t
open database files

My best setup so far has been to install in the following order

1. Fresh Windows install
2. In our case we're using Novell as a networking O.S., so, I load the novell client next, Ver. 4.83 or Ver. 4.
along with Zenworks 3.2 or 4.0 (yes, I know the, "BAD" "N"-word!!!)
3. Install all windows O.S. and I.E. updates, etc.
4. Install Visual Studio
5. Re-apply latest windows O.S. service packs
6. Install Visual Studio 6, SP
7. Install MS Office XP
8. Install MS Office XP updates and service packs
9. Install WCU (Windows Component Updates) for VS .NET
10. Install VS .NE
11. Check install for VS .NET updates and Service Packs
12. Go into the .NET framework MMC, then go to, My Computer, Code Groups, All_Code, LocalIntranet, Choose
"Edit Code Group Properties", Select "Permission Set" tab, and change it to, "Fulltrust"
13. Go into the .NET framework 1.1 MMC, then into, My Computer, Code Groups, All_Code, LocalIntranet, Choose
"Edit Code Group Properties", Select "Permission Set" tab, and change it to, "Fulltrust"

NOTE: I've often wondered if I need to have both versions of the .NET framework on the machine. I notice that, whe
you run all of the windows, updates, you get an MMC for, "Microsoft .NET framework confiuration", and after you instal
the WCU for Visual Studio .NET and Visual Studio .NET, you also have an MMC for "Microsoft .NET framework 1.1
Configuration" installed onto the machine

Usually after this process, things seem as though they are working together, but then my users start to have issue
with compiling projects in Visual Studio 6 and also debugging projects in Visual Studio 6 while the functionality o
Visual Studio .NET seems to be alright

I am installing Visual Studio .NET and Visual Studio 6 into seperate directories by just letting the installer programs us
their defaults on the machine

The standard user on my machine DOES NOT have administrative rights, but I do place, "\\machine name\authenticated users" as members of BOTH the "Debug User's" group and the, "Software Developer's group" where "machine name" i
the Microsoft name for the machine. We do usually put an underscore in the machine name as well. Our machines D
NOT run Microsoft File and Print Sharing nor do they have the Microsoft Client or the Microsoft Family login installed on
them

Another thing I can do is run the program as the local, "system" user if I run the program through Novell's NAL syste
(Novell Application Launcher). Note: for those of you who don't know, Zenworks for Desktops and it's NAL is Novell'
answer to Microsoft's, SMS (Systems Management Server) system. This has caused us some issues as Novell's metho
of authenticating users isn't always "in sync." with Windows authentication. Because of this, the applications we run wit
the, NAL, particularly when we run them with, "System" user privileges, sometimes have issues connecting to and seeing
files on network drives. Windows seems to be fine with the, "system" user, but NOVELL isn't allowing access (all of ou
network drives are on NOVELL servers) because the machine knows about the, "system" user, but Novell doesn't

I know we may be able to change the workstation name to NOT have an underscore in it (an underscore in a machin
name IS NOT what Microsoft recommends), but I doubt very seriously that my management is going to be willing t
part with Novell or Zenworks for Desktops for quite some time

Any and all help you folks could think of would be great!!

Paul Kattni
pkattnig (AT) mesastate (DOT) ed

P.S. Yes, I have checked for answers on Novell's support websites

"pkattnig (AT) mesastate (DOT) edu" <anonymous (AT) discussions (DOT) microsoft.com> wrote in
message news:F7F4ED77-69E2-4A18-8590-093E601FA488 (AT) microsoft (DOT) com...
"Debug User's" group and the, "Software Developer's group" where "machine
name" is
This description certainly expands on your original topic and presents many
additional possibilities that I cannot address, as we don't use Office XP or
Novell.
If you don't get more feedback here, I do think this alternative group,

microsoft.public.vsnet.setup

may generate some interest.

--
Peter [MVP Academic]