SqlConnection component in VB.2005

[Roman]

Hello

I have a component built in VB.2003. It has the following property:

Public Shared mCONN As SqlConnection
Public Property Connection() As SqlConnection
Get
Return mCONN
End Get
Set(ByVal value As SqlConnection)
mCONN = value
End Set
End Property

In VB.2003 there was a SqlConnection component. Once confugured it would
automatically show in my custom component under Connection property.

VB.2005 does not have SqlConnection component and my Connection property is
always empty. Is there a way to get around this limitation in vs.2005?

Thanks in advance,
Roman

[Ken Tucker [MVP]]

Hi,

The SqlConnection was replaced with table adapters in VB 2005. Maybe
you can extend a tableadapter to suite your needs.

http://msdn2.microsoft.com/en-us/library/ms233697.aspx

Ken
-------------------
"Roman" <[ro****@mbsnetin c.com]> wrote in message
news:Oo******** ******@TK2MSFTN GP10.phx.gbl...

Hello

I have a component built in VB.2003. It has the following property:

Public Shared mCONN As SqlConnection
Public Property Connection() As SqlConnection
Get
Return mCONN
End Get
Set(ByVal value As SqlConnection)
mCONN = value
End Set
End Property

In VB.2003 there was a SqlConnection component. Once confugured it would
automatically show in my custom component under Connection property.

VB.2005 does not have SqlConnection component and my Connection property
is
always empty. Is there a way to get around this limitation in vs.2005?

Thanks in advance,
Roman

[landers]

Yuck!

Do you know why Microsoft would release a new version of a language and not
make it backward compatible?

IMO, it actions like these that make it hard for developers to move forward.
New versions of languages should be merely enhancements and bug fixes. To
take major sections out of a language like the SqlConnection is madness.
Developers that have developed large applications in 2003 will have to make
code changes, and potentially, pattern changes in order for their
applications to work in 2005! I know this my opinion, but here's another
one ... Yuck! I am sticking to 2003 until Microsoft decide to fix the nasty
bugs 2005 and start putting their feet firmly on the ground and start
implementing backward compatibility.

L.

"Ken Tucker [MVP]" <vb***@bellsout h.net> wrote in message
news:eC******** *****@TK2MSFTNG P12.phx.gbl...

Hi,

The SqlConnection was replaced with table adapters in VB 2005.
Maybe you can extend a tableadapter to suite your needs.

http://msdn2.microsoft.com/en-us/library/ms233697.aspx

Ken
-------------------
"Roman" <[ro****@mbsnetin c.com]> wrote in message
news:Oo******** ******@TK2MSFTN GP10.phx.gbl...

Hello

I have a component built in VB.2003. It has the following property:

Public Shared mCONN As SqlConnection
Public Property Connection() As SqlConnection
Get
Return mCONN
End Get
Set(ByVal value As SqlConnection)
mCONN = value
End Set
End Property

In VB.2003 there was a SqlConnection component. Once confugured it would
automatically show in my custom component under Connection property.

VB.2005 does not have SqlConnection component and my Connection property
is
always empty. Is there a way to get around this limitation in vs.2005?

Thanks in advance,
Roman

[Dennis]

I was under the impression that you could start a vb.net 2003 solution under
vb.net 2005 and it would convert seamlessly. This is apparently not the case
since SqlConnection is not supported in VB.Net 2005.
--
Dennis in Houston
"Ken Tucker [MVP]" wrote:

Hi,

The SqlConnection was replaced with table adapters in VB 2005. Maybe
you can extend a tableadapter to suite your needs.

http://msdn2.microsoft.com/en-us/library/ms233697.aspx

Ken
-------------------
"Roman" <[ro****@mbsnetin c.com]> wrote in message
news:Oo******** ******@TK2MSFTN GP10.phx.gbl...

Hello

I have a component built in VB.2003. It has the following property:

Public Shared mCONN As SqlConnection
Public Property Connection() As SqlConnection
Get
Return mCONN
End Get
Set(ByVal value As SqlConnection)
mCONN = value
End Set
End Property

In VB.2003 there was a SqlConnection component. Once confugured it would
automatically show in my custom component under Connection property.

VB.2005 does not have SqlConnection component and my Connection property
is
always empty. Is there a way to get around this limitation in vs.2005?

Thanks in advance,
Roman

[Kerry Moorman]

Ken,

I haven't used VS2005 yet, but I'm virtually certain that there is still a
SQLConnection object as part of ADO.Net 2.0.

Perhaps you mean that there is no longer some visual designer
component/wizard that represents a SQLConnection? But I'm sure you can still
dimension a variable as a new SQLConnection.

Kerry Moorman
"Ken Tucker [MVP]" wrote:

Hi,

The SqlConnection was replaced with table adapters in VB 2005. Maybe
you can extend a tableadapter to suite your needs.

http://msdn2.microsoft.com/en-us/library/ms233697.aspx

Ken
-------------------
"Roman" <[ro****@mbsnetin c.com]> wrote in message
news:Oo******** ******@TK2MSFTN GP10.phx.gbl...

Hello

I have a component built in VB.2003. It has the following property:

Public Shared mCONN As SqlConnection
Public Property Connection() As SqlConnection
Get
Return mCONN
End Get
Set(ByVal value As SqlConnection)
mCONN = value
End Set
End Property

In VB.2003 there was a SqlConnection component. Once confugured it would
automatically show in my custom component under Connection property.

VB.2005 does not have SqlConnection component and my Connection property
is
always empty. Is there a way to get around this limitation in vs.2005?

Thanks in advance,
Roman

[Lucky]

guys,
even i've not used vs2005 but i've just checked this thing out and
found that IT IS STILL THERE. all you neeed to do is, goto add item and
add the components on your toolbox. bydefault you wont find then on the
toolbox. and aslo the GUI support is there so you stil can adjust
params through GUI.
Lucky

[Lucky]

by the way i forgot to mention that i'm using VS2005 Beta 2. i dont
know which version of VS 2005 you have. but in Beta 2 release it it
there

[Ken Tucker [MVP]]

Hi,

Yes it will convert fine. They sqlconnection in the
system.data.sql client namespace and the sqlconnection component in the
toolbox are still there. The component for connecting to data in the ide
is the tableadapter. The new model is much better.

http://msdn2.microsoft.com/en-us/library/bz9tthwx.aspx

Ken
--------------
"Dennis" <De****@discuss ions.microsoft. com> wrote in message
news:63******** *************** ***********@mic rosoft.com...

I was under the impression that you could start a vb.net 2003 solution
under
vb.net 2005 and it would convert seamlessly. This is apparently not the
case
since SqlConnection is not supported in VB.Net 2005.
--
Dennis in Houston
"Ken Tucker [MVP]" wrote:

Hi,

The SqlConnection was replaced with table adapters in VB 2005.
Maybe
you can extend a tableadapter to suite your needs.

http://msdn2.microsoft.com/en-us/library/ms233697.aspx

Ken
-------------------
"Roman" <[ro****@mbsnetin c.com]> wrote in message
news:Oo******** ******@TK2MSFTN GP10.phx.gbl...

> Hello
>
> I have a component built in VB.2003. It has the following property:
>
> Public Shared mCONN As SqlConnection
> Public Property Connection() As SqlConnection
> Get
> Return mCONN
> End Get
> Set(ByVal value As SqlConnection)
> mCONN = value
> End Set
> End Property
>
> In VB.2003 there was a SqlConnection component. Once confugured it
> would
> automatically show in my custom component under Connection property.
>
> VB.2005 does not have SqlConnection component and my Connection
> property
> is
> always empty. Is there a way to get around this limitation in vs.2005?
>
> Thanks in advance,
> Roman
>
>

[Ken Tucker [MVP]]

Hi,

You are right they are still there. My thought was he should try
and use the new data binding model in the ide rather than expect the user of
his control to add additional components to the toolbox.

Ken
---------------------
"Kerry Moorman" <Ke**********@d iscussions.micr osoft.com> wrote in message
news:CE******** *************** ***********@mic rosoft.com...

Ken,

I haven't used VS2005 yet, but I'm virtually certain that there is still a
SQLConnection object as part of ADO.Net 2.0.

Perhaps you mean that there is no longer some visual designer
component/wizard that represents a SQLConnection? But I'm sure you can
still
dimension a variable as a new SQLConnection.

Kerry Moorman
"Ken Tucker [MVP]" wrote:

Hi,

The SqlConnection was replaced with table adapters in VB 2005.
Maybe
you can extend a tableadapter to suite your needs.

http://msdn2.microsoft.com/en-us/library/ms233697.aspx

Ken
-------------------
"Roman" <[ro****@mbsnetin c.com]> wrote in message
news:Oo******** ******@TK2MSFTN GP10.phx.gbl...

> Hello
>
> I have a component built in VB.2003. It has the following property:
>
> Public Shared mCONN As SqlConnection
> Public Property Connection() As SqlConnection
> Get
> Return mCONN
> End Get
> Set(ByVal value As SqlConnection)
> mCONN = value
> End Set
> End Property
>
> In VB.2003 there was a SqlConnection component. Once confugured it
> would
> automatically show in my custom component under Connection property.
>
> VB.2005 does not have SqlConnection component and my Connection
> property
> is
> always empty. Is there a way to get around this limitation in vs.2005?
>
> Thanks in advance,
> Roman
>
>

[Roman]

Hi guys

Thanks for all your suggestions.
I will definitely try the new data access features available in vb.2005.
But that will require recoding many parts of my component which was
compelete and ready for use in vb.2003. Just to save time I will manually
add
the SqlConnection to my toolbox. I never knew it was still there!

Thanks again
Roman

"Ken Tucker [MVP]" <vb***@bellsout h.net> wrote in message
news:%2******** *******@TK2MSFT NGP09.phx.gbl.. .

Hi,

You are right they are still there. My thought was he should try
and use the new data binding model in the ide rather than expect the user
of his control to add additional components to the toolbox.

Ken
---------------------
"Kerry Moorman" <Ke**********@d iscussions.micr osoft.com> wrote in message
news:CE******** *************** ***********@mic rosoft.com...

Ken,

I haven't used VS2005 yet, but I'm virtually certain that there is still
a
SQLConnection object as part of ADO.Net 2.0.

Perhaps you mean that there is no longer some visual designer
component/wizard that represents a SQLConnection? But I'm sure you can
still
dimension a variable as a new SQLConnection.

Kerry Moorman
"Ken Tucker [MVP]" wrote:

Hi,

The SqlConnection was replaced with table adapters in VB 2005.
Maybe
you can extend a tableadapter to suite your needs.

http://msdn2.microsoft.com/en-us/library/ms233697.aspx

Ken
-------------------
"Roman" <[ro****@mbsnetin c.com]> wrote in message
news:Oo******** ******@TK2MSFTN GP10.phx.gbl...
> Hello
>
> I have a component built in VB.2003. It has the following property:
>
> Public Shared mCONN As SqlConnection
> Public Property Connection() As SqlConnection
> Get
> Return mCONN
> End Get
> Set(ByVal value As SqlConnection)
> mCONN = value
> End Set
> End Property
>
> In VB.2003 there was a SqlConnection component. Once confugured it
> would
> automatically show in my custom component under Connection property.
>
> VB.2005 does not have SqlConnection component and my Connection
> property
> is
> always empty. Is there a way to get around this limitation in vs.2005?
>
> Thanks in advance,
> Roman
>
>