Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

VB6 cohabitate with Visual Studio 2005?

1 view
Skip to first unread message

rick-...@uiowa.edu

unread,
Dec 15, 2009, 1:05:02 PM12/15/09
to
I have VB 6 professional edition installed and I'm pretty happy with
it. But I have an upcoming project using a book where the author used
Visual Studio 2005 and some tools not avaiable in the older VB6. Can
I install both on the same computer without conflicts?

Thanks.

Auric__

unread,
Dec 15, 2009, 1:19:56 PM12/15/09
to

Yes.

--
"Lonely Tylenol" is a palindrome.
I had to look it up so don't credit me.

Ralph

unread,
Dec 15, 2009, 7:10:56 PM12/15/09
to

<rick-...@uiowa.edu> wrote in message
news:fa5e39e7-f753-4d95...@k4g2000yqb.googlegroups.com...

Auric_ is essentially correct, there is no major conflict.

The only issue, which may or may not effect you, is that the VSNet install
will re-associate some file extenstions to point to its own tools. This
effects mostly VC as both the older VC and dotNet versions shares the same
file extensions. dotNet uses different file extensions for its VB.Net
language. But it can effect any secondary tools you might be using for Html,
rc, etc. files.

Usually not a problem, but can appear mysterious if you are not expecting
it.

-ralph


Auric__

unread,
Dec 15, 2009, 7:36:21 PM12/15/09
to
On Wed, 16 Dec 2009 00:10:56 GMT, Ralph wrote:

> <rick-...@uiowa.edu> wrote in message
> news:fa5e39e7-f753-4d95...@k4g2000yqb.googlegroups.com...
>> I have VB 6 professional edition installed and I'm pretty happy with
>> it. But I have an upcoming project using a book where the author used
>> Visual Studio 2005 and some tools not avaiable in the older VB6. Can
>> I install both on the same computer without conflicts?
>>
>> Thanks.
>
> Auric_ is essentially correct, there is no major conflict.

Two underscores, please. A-u-r-i-c-_-_. I'm picky like that.

> The only issue, which may or may not effect you, is that the VSNet
> install will re-associate some file extenstions to point to its own
> tools. This effects mostly VC as both the older VC and dotNet versions
> shares the same file extensions. dotNet uses different file extensions
> for its VB.Net language. But it can effect any secondary tools you might
> be using for Html, rc, etc. files.
>
> Usually not a problem, but can appear mysterious if you are not
> expecting it.

I wasn't aware of that little tidbit. When I install VB.Net (a rare
occurrence, to be sure) I don't pay much attention to what file associations
are affected, beyond the usual VB ones.

--
If at first you don't succeed, skydiving is not for you.

0 new messages