I would like to install Visual Studio 6.0 onto the Vista computer but I keep
getting errors cannot load module when loading my apps also a message comes
up cannot register OLE object. I need to support my VB 6 apps on Vist
computers so I need to be able to debug them on a Vist machine so is there
any solution to this????

Thanks
Lorne

"Lorne Merner" <mernerl********.com> wrote in message
news:eHhEPTbkHHA.4152@TK2MSFTNGP04.phx.gbl...[color=blue]
>I would like to install Visual Studio 6.0 onto the Vista computer but I
>keep getting errors cannot load module when loading my apps also a message
>comes up cannot register OLE object. I need to support my VB 6 apps on
>Vist computers so I need to be able to debug them on a Vist machine so is
>there any solution to this????
>[/color]

You need to install with elevated privileges according to this link ,
because the OP finally replied that there was success with the install of VS
6.

[url]http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1192228&SiteID=1[/url]

"Lorne Merner" <mernerl********.com> wrote in message
news:eHhEPTbkHHA.4152@TK2MSFTNGP04.phx.gbl...
[color=blue]
>I would like to install Visual Studio 6.0 onto the Vista computer but I
>keep getting errors cannot load module when loading my apps also a message
>comes up cannot register OLE object. I need to support my VB 6 apps on
>Vist computers so I need to be able to debug them on a Vist machine so is
>there any solution to this????[/color]

This *is* possible, though as Mr Arnold said, you'll need to install and run
with elevated privileges etc...

A possible alternative solution: do you have a decent amount of RAM on your
Vista machine, as well as a licensed copy of WinXP / Win2k?

If so, have you considered Microsoft Virtual PC...?
[url]http://www.microsoft.com/windows/products/winfamily/virtualpc/default.mspx[/url]

That would allow you to create a virtual machine, install an earlier version
of Windows, and then Visual Studio 6 would work exactly as it always did...
In fact, it wouldn't have the slightest notion that it was running in a
virtual machine... The virtual machine would sit on your network just like a
real machine...

I'm currently in the process of upgrading an old VB6 app which I wrote
nearly ten years ago (yes, really!) to C#, and VPC is just perfect for this
sort of scenario - I have the old version running in Win2k and the new
version running in 64-bit Vista side by side...

In addition, I still support several legacy systems (one of which uses NT4,
IIS3, MTS2 & SQL Server 6.5!!!), and Virtual PC is just perfect for this...

--
[url]http://www.markrae.net[/url]

<snipped>
[color=blue]
> A possible alternative solution: do you have a decent amount of RAM on
> your Vista machine, as well as a licensed copy of WinXP / Win2k?
>
> If so, have you considered Microsoft Virtual PC...?
> [url]http://www.microsoft.com/windows/products/winfamily/virtualpc/default.mspx[/url]
>
> That would allow you to create a virtual machine, install an earlier
> version of Windows, and then Visual Studio 6 would work exactly as it
> always did... In fact, it wouldn't have the slightest notion that it was
> running in a virtual machine... The virtual machine would sit on your
> network just like a real machine...[/color]

Although, this solution may work, I don't think it's a good idea. The reason
I say this is because of using an install package that will select
automatically or the developer will select the required Dll(s) that will
make said application install and work.

This is a VB 6 solution and Dll(s) must be registered that most likely will
include common Dll(s) and O/S Dll(s) specific for the O/S platform it is
running on. One cannot take Dll(s) that were intended to run on a specific
platform such as XP and expect those Dll(s) to install and work on the Win
2k platform, the Vista platform, or the other way around.

In the case of VS 6, the application must be developed on the targeted
platform it is intended to run on, because those Dll(s) must be registered.

Application developed on Vista to run on the Vista platform. Application
developed on XP to run on the XP platform, etc, etc.

Otherwise, you're just creating a Dll Hell situation, where Dll(s) replace
other Dll(s) causing applications to break and not work anymore.