Visual Basic

button and combobox in a Component

27-Jun-07 5:02

That depeds on the type of server you're getting this image from and how you're displaying this image.

A guide to posting questions on CodeProject[^]

Dave Kreskowiak
Microsoft MVP
Visual Developer - Visual Basic
2006, 2007

Typed Dataset

ShuklaGirish26-Jun-07 23:36

ShuklaGirish

26-Jun-07 23:36

How to create Typed dataset through code.

anujose26-Jun-07 23:13

anujose

26-Jun-07 23:13

in one component i want to place one button and combobox .how can i do that?..........i don't want to do as a usercontrol...is their any way to do like this?............

Pls help me.it's very urgent................

Tamimi - Code26-Jun-07 23:36

Tamimi - Code

26-Jun-07 23:36

are you working with WebForm or WinForm ??

When you get mad...THINK twice that the only advice
Tamimi - Code

anujose26-Jun-07 23:39

anujose

26-Jun-07 23:39

Winform

Tamimi - Code26-Jun-07 23:51

Tamimi - Code

26-Jun-07 23:51

i have the soluotion for the web case Roll eyes | :rolleyes:

When you get mad...THINK twice that the only advice
Tamimi - Code

Craster26-Jun-07 23:47

Craster

26-Jun-07 23:47

If you want a control that 'contains' other controls, then you want a usercontrol. Why don't you want to do this?

Dave Kreskowiak27-Jun-07 3:50

There must be a better way to enter lots of strongly typed properties in a class

27-Jun-07 3:50

anujose wrote:
i don't want to do as a usercontrol...

You have two choices. Either inheriting from UserControl or write the entire thing from scratch, inheriting from Control.

A guide to posting questions on CodeProject[^]

Dave Kreskowiak
Microsoft MVP
Visual Developer - Visual Basic
2006, 2007

MartyK200726-Jun-07 22:41

Re: There must be a better way to enter lots of strongly typed properties in a class

26-Jun-07 22:41

Hello,
I am trying to write a strongly typed object class
(so I can bind the properties of the class object to form controls) along the lines of:

Public Class foo
Private _myCol As Collection
Public Property Name() As String
Get
Return _myCol("Name")
End Get
Set(ByVal value As String)
_myCol.Remove("Name")
_myCol.Add(value, "Name")
End Set
End Property
Public Property Title() As String
Get
Return _myCol("Title")
End Get
Set(ByVal value As String)
_myCol.Remove("Title")
_myCol.Add(value, "Title")
End Set
End Property
End Class

This is quite simply awful. If I use an array instead of a collection I can get rid of the
collection remove and add rubbish.
In effect I could replace
Return _myCol("Title")
with
Return _myArray(1)

This means that I have to relate each property to an index (Name to 1 and Title to 2 for example)
and it means that when I create the class I have to manually type this relationship in.

The real problem with this is that I anticpate having lots of classes like this each with lots
of properties and frankly I am a bit lazy and dont want to physically key them in like this.

One option was to bind the controls to an exposed dataset in my foo class instead but I dont
want to do that. I want to expose Foo.Name and Foo.Title etc.

There must be an easier way than that above - any ideas?? (either a template based way of entering
them into visual studio or a completly new way of coding them)

thanks in advance
Martin

-- modified at 5:25 Wednesday 27th June, 2007

life is a bowl of cherries
go on take a byte

MohammadAmiry27-Jun-07 0:41

MohammadAmiry

27-Jun-07 0:41

Why don't you create a structure with the properties you like, i.e.

<code>
Class _MyProperies
 Public Title, Name, etc As String
End Class
</code>

And then in your foo class define an array of this type
Private _MyArray As _MyProperties()

Does this help you?

Re: There must be a better way to enter lots of strongly typed properties in a class

MartyK200727-Jun-07 1:06

Re: There must be a better way to enter lots of strongly typed properties in a class

27-Jun-07 1:06

Hi,
thanks for that but it doesnt really

my foo properties woud be

Public Property Name ...
get ..
return _Myarry(Index)
....

so for each property I would need to key in name and the index in a couple of places

I was hoping to avoid that for 2 reasons
1.. I dont like saying property Name is Index 1 in the _MyArray - Its just ugly
2.. I am lazy and dont like keying in Name and index for every property in every class

any other ideas??
thanks
Martin

life is a bowl of cherries
go on take a byte

Taylor Kobani27-Jun-07 1:55

Taylor Kobani

27-Jun-07 1:55

Private C As New Collection<br />
    Property MyProperties(ByVal i As String) As String<br />
        Get<br />
            Return C(i)<br />
        End Get<br />
        Set(ByVal value As String)<br />
            Try<br />
                C.Remove(i)<br />
            Catch ex As Exception<br />
            Finally<br />
                C.Add(value, i)<br />
            End Try<br />
        End Set<br />
    End Property

A.E.K

Re: There must be a better way to enter lots of strongly typed properties in a class

MartyK200727-Jun-07 2:04

Re: There must be a better way to enter lots of strongly typed properties in a class

27-Jun-07 2:04

Hi,
Thanks for that but any code using foo class would have to do
foo.MyProperties("Name") = "John"

I absolutley need the outside world to see it as strongly typed properties
such as Foo.Name and Foo.Type.

This is because the classes will be used as business objects and I may wish
to add extra code to one or two of a classes properties later on . I dont want a big case statement in the properties code (or indeed a function called by the properties code).

thanks anyway
Martin

life is a bowl of cherries
go on take a byte

Dave Kreskowiak27-Jun-07 3:49

Re: There must be a better way to enter lots of strongly typed properties in a class

27-Jun-07 3:49

In that case, you could do two classes. One for an instance of the object that holds all the properties and a second as a collection of those objects. The .NET Framework uses a setup like this extensively.

A guide to posting questions on CodeProject[^]

Dave Kreskowiak
Microsoft MVP
Visual Developer - Visual Basic
2006, 2007

MartyK200727-Jun-07 3:53

Re: There must be a better way to enter lots of strongly typed properties in a class

27-Jun-07 3:53

Sorry dave,
I'm not quite following how that would work
can you give me a snippet

I dont see how it makes adifference if its one Foo object or a collection of foo objects. Foo.Name still needs to get to a varaible or internal collection

I have just been reading up on intellisense code snippets that is in effect a template for my class and that may help

thanks
Martin

life is a bowl of cherries
go on take a byte

Dave Kreskowiak27-Jun-07 4:10

Re: There must be a better way to enter lots of strongly typed properties in a class

27-Jun-07 4:10

For the Person:

Public Class Person
    Private _Name As String
    Private _Title As String
 
    Public Property Name As String
    ...
    Public Property Title As String
    ...
End Class

For the Collection of Persons (simplified)

Public Class PersonsCollection
    Implements IList, ICollection, IEnumerable
 
    Private Persons As Person()
    Private PersonsCount As Integer
 
    Public Sub New()
    End Sub
 
    Public Overridable Sub Add(ByVal person As Person)
       ...
    End Sub
 
    ...
End Class

Of course, in 2005, you can skip the collection and just use a typed collection instead:

Dim Persons As New List(Of Person)

A guide to posting questions on CodeProject[^]

Dave Kreskowiak
Microsoft MVP
Visual Developer - Visual Basic
2006, 2007

MartyK200727-Jun-07 4:31

Re: There must be a better way to enter lots of strongly typed properties in a class

27-Jun-07 4:31

Hi
my problem is in here
Public Class Person
Private _Name As String
Private _Title As String

Public Property Name As String
get
return _name

set (value..)
_name = value

In this property I have enterd Name once and _Name twice.
now this is fine for one or two properties but when you have 80 of these properties in a class and you need to create many classes then typing it in becomes painfull.

I think the code snippet will help but I was hoping for some kind of generator where
I could key in a list and have a class created for me with those properties set from the list.

End Class

thanks
Martin

life is a bowl of cherries
go on take a byte

Dave Kreskowiak27-Jun-07 5:01

Re: There must be a better way to enter lots of strongly typed properties in a class [modified]

27-Jun-07 5:01

MartyK2007 wrote:
In this property I have enterd Name once and _Name twice.
now this is fine for one or two properties but when you have 80 of these properties in a class and you need to create many classes then typing it in becomes painfull.

A generator or two might exist, but I don't know of any. Try Googling for "VB.NET Property code generation".

A guide to posting questions on CodeProject[^]

Dave Kreskowiak
Microsoft MVP
Visual Developer - Visual Basic
2006, 2007

Taylor Kobani27-Jun-07 6:46

Taylor Kobani

27-Jun-07 6:46

Write another program that gets the name of the properties ,adds them to a list and finally makes the code for you to add to your class.

The function below may help you

Function Generate(ByVal mc As Collection) As String
        Dim str As String
        For i As Integer = 1 To mc.Count

            str &= "Public Property " & mc(i) & "() As String" * vbCrLf & _
"Get" & vbCrLf & "Return MyDataCol(""" & mc(i) & """)" & vbCrLf & _
"End Get" & vbCrLf & "Set(ByVal value As String)" & vbCrLf & _
"MyDataCol.Remove(""" & mc(i) & """)" & vbCrLf & "MyDataCol.Add(value, """ & mc(i) & """)" & _
vbCrLf & "End Set" & vbCrLf & "End Property" & vbCrLf
        Next

        Return str
    End Function

where mc is a collection of property names

A.E.K

Re: There must be a better way to enter lots of strongly typed properties in a class

Dave Kreskowiak27-Jun-07 7:09