vb.net controls: Using VB.Net User control in vb6 -- vb.net controls

You're in the

vb.net controls

group:

Using VB.Net User control in vb6

Using VB.Net User control in vb6

Duncan
6/20/2006 12:00:00 AM

vb.net controls:

Dear All
I would like to use a user control built in vb.net 2005 in vb6 sp 6. Is
this possible ? if yes can you please show how it is done?

Duncan Dimech

Re: Using VB.Net User control in vb6

Herfried K. Wagner [MVP]
6/20/2006 3:11:53 PM

"Duncan" <ddimech@ads.com.mt> schrieb:
[quoted text, click to view]

This scenario is not supported.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>

Re: Using VB.Net User control in vb6

MikeD
6/20/2006 6:29:25 PM

[quoted text, click to view]

You sure about that? I thought you could. Of course, I don't know how much
sense it actually makes. Seems a little silly to put a requirement like the
..NET 2.0 Framework on your VB6 app just to use a control.

--
Mike
Microsoft MVP Visual Basic

Re: Using VB.Net User control in vb6

Michael Cole
6/21/2006 12:00:00 AM

[quoted text, click to view]

The scenario is not _supported_. Much like VB6 is not _supported_. Its not
whether you can do it, its whether MS _wants_ you to do it. :-)

Microsoft - Where do _we_ want you to go today....

[For those with a humour bypass - don't take this post seriously]

--
Regards,

Michael Cole

Re: Using VB.Net User control in vb6

Duncan
6/21/2006 12:00:00 AM

The reason why we want to do this is mainly because the upgrade wizard
Microsoft provided from VB6 to VB.Net makes it not worth the hassle.

Second - a new project built in VB.NET 2005 requires to use a routine of
another project built in VB6 - we cannot afford to have two different
results, plus the vb6 routine is tested and we know that it matches the
client needs. If a change occurs in the business logic it has to be for
both the same - so the options really are to use VB6 control in dot net ot
VB.Net in VB6.

Duncan

[quoted text, click to view]

Re: Using VB.Net User control in vb6

Ralph
6/21/2006 11:08:04 AM

[quoted text, click to view]
<snipped>

IMHO: Using the ".ocx" within a dotNet will be the sanier option on the long
run. Open the toolbox, add the component, and test it.

However, be aware that it must be a very "well-behaved" and
"default-complete" OCX. In our experience it is not uncommon that VB6 custom
created controls need to be revisited and adjusted. Especially with
design-time properties and behaviors. The VB6 IDE appears to be more
forgiving.

Perhaps, mostly because of familiarity, it is easier and less fustrating to
make an OCX that dotNet can work with, than vice versa.

hth
-ralph

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the vb.net controls group.

home · blog · groups

Questions? Comments? Contact the dn