The idea to create a base form to keep all development looking the same great but the articles raises more questions than it answers. For people not use to creating inherited controls the following should be described;
"The base form should typically be located in a class library project"
Q: How is this done ?
"set the Modifier property to Public or Protected."
Q: What is the modifier Property and how do I change it.
"create the derived form, simply add a new inherited form to your project"
Q:How ?
"This will launch the inheritance picker"
Q: What is that ..how is it used.
I hate it when some one comes up with something good but doesn't explain enough so I can go try it out. I would take me a while to look up all these things in .NET help so i could make a base form. A link in the article would have been so much simpler.
Regards
Josef
Discussion on:
View:
Show:
This sample demostrate that the OO is arrived for all.
Personally I'm very satysfated and use it, and in this way is just automatic!
Maybe someone said: "You are not a programmer becouse you write too few code."
I said: "I'm happy to think other solution, and not repeat the same thinghs all days."
Ciao (excuse my eng)
Personally I'm very satysfated and use it, and in this way is just automatic!
Maybe someone said: "You are not a programmer becouse you write too few code."
I said: "I'm happy to think other solution, and not repeat the same thinghs all days."
Ciao (excuse my eng)
The idea to create a base form to keep all development looking the same great but the articles raises more questions than it answers. For people not use to creating inherited controls the following should be described;
"The base form should typically be located in a class library project"
Q: How is this done ?
"set the Modifier property to Public or Protected."
Q: What is the modifier Property and how do I change it.
"create the derived form, simply add a new inherited form to your project"
Q:How ?
"This will launch the inheritance picker"
Q: What is that ..how is it used.
I hate it when some one comes up with something good but doesn't explain enough so I can go try it out. I would take me a while to look up all these things in .NET help so i could make a base form. A link in the article would have been so much simpler.
Regards
Josef
"The base form should typically be located in a class library project"
Q: How is this done ?
"set the Modifier property to Public or Protected."
Q: What is the modifier Property and how do I change it.
"create the derived form, simply add a new inherited form to your project"
Q:How ?
"This will launch the inheritance picker"
Q: What is that ..how is it used.
I hate it when some one comes up with something good but doesn't explain enough so I can go try it out. I would take me a while to look up all these things in .NET help so i could make a base form. A link in the article would have been so much simpler.
Regards
Josef
I personally think the article was very helpful. It doesn't have to be explained from scratch, since it is assumed you have some BASIC knowledge at least. I understood it clearly, and I am completely new to VB.NET. I enjoyed it and hope to see more of these.
The idea to create a base form to keep all development looking the same great but the articles raises more questions than it answers. For people not use to creating inherited controls the following should be described;
"The base form should typically be located in a class library project"
Q: How is this done ?
"set the Modifier property to Public or Protected."
Q: What is the modifier Property and how do I change it.
"create the derived form, simply add a new inherited form to your project"
Q:How ?
"This will launch the inheritance picker"
Q: What is that ..how is it used.
I hate it when some one comes up with something good but doesn't explain enough so I can go try it out. I would take me a while to look up all these things in .NET help so i could make a base form. A link in the article would have been so much simpler.
Regards
Josef
"The base form should typically be located in a class library project"
Q: How is this done ?
"set the Modifier property to Public or Protected."
Q: What is the modifier Property and how do I change it.
"create the derived form, simply add a new inherited form to your project"
Q:How ?
"This will launch the inheritance picker"
Q: What is that ..how is it used.
I hate it when some one comes up with something good but doesn't explain enough so I can go try it out. I would take me a while to look up all these things in .NET help so i could make a base form. A link in the article would have been so much simpler.
Regards
Josef
Josef,
The articles on this site assumes that you have some working knowledge of VS.NET
1.) A class library is a normal DLL project.
2.) All properties can be set in the Property Browser.
3.) Create a standard form and just change the objectit inherrits from, or use the Inherritance picker.
Cheers,
Charl
The articles on this site assumes that you have some working knowledge of VS.NET
1.) A class library is a normal DLL project.
2.) All properties can be set in the Property Browser.
3.) Create a standard form and just change the objectit inherrits from, or use the Inherritance picker.
Cheers,
Charl
Hi. I add a form to my proyect. Then I add a dataset, a dataviewmanager and a simple text box binded to a column in a table in the dataset (using the 'text' property).
When inheriting throws the following error:
Can't bind to property "Text" because it is read only.
Parameter name: PropertyName
I have to say the textbox isn't set to readonly. I tryied this with other controls I usually use [like datetimepicker] and I ended up with the same results while trying to inherit.
J. Germano
When inheriting throws the following error:
Can't bind to property "Text" because it is read only.
Parameter name: PropertyName
I have to say the textbox isn't set to readonly. I tryied this with other controls I usually use [like datetimepicker] and I ended up with the same results while trying to inherit.
J. Germano
Nevermind, the bound control needs the Public property instead of the default one Friend.
J. Germano
PS: I know, it's not binded, it's bound. Big laughter from all the non-english speakers
J. Germano
PS: I know, it's not binded, it's bound. Big laughter from all the non-english speakers
I know you're happy to see this and all, but...
FoxPro's had visual inheritance for years
FoxPro's had visual inheritance for years
I used Fox 6 and enjoyed using the program Moreover, you're correct in your assertion that Fox has had V.I.(I didn't know for how long, thanks for that fact).
I'll fling my .02 into the ring and remind the vb.net gang (I've tossed all MS programming tools with the exception of Access -quick prototyping) that Delphi has had all of the "MS innovations" used to turn vb into vb.net for quite a long time.
No, I'm not advocating a language/flame war!
Everyone should use what they enjoy, period.
To qualify: I was a VB guy for 6 years. In fact, I learned to program with VB; I went the Rod Stephens route not long after vb6 (-:
I'll fling my .02 into the ring and remind the vb.net gang (I've tossed all MS programming tools with the exception of Access -quick prototyping) that Delphi has had all of the "MS innovations" used to turn vb into vb.net for quite a long time.
No, I'm not advocating a language/flame war!
Everyone should use what they enjoy, period.
To qualify: I was a VB guy for 6 years. In fact, I learned to program with VB; I went the Rod Stephens route not long after vb6 (-:
my company moved to .net a year ago, and as a Delphi guy I had to change or get another job. but to my suprise, it was rather easy moving to vb.net because most of the NEW stuff is just enhancements to what Delphi has; but it shouldn't be suprising,check who engineered vb.net
I thought the article was very good, I have already started using inheritance in my VB.Net projects and am soo glad that I am finally able to Object Orient my programming withough having to learn a whole new language to boot. I Know VB.Net is different enough but for a VB programmer the step up to OOP is easier since I am already familiar enough with the base language.
One thing I have noticed though is that C# allows multiple Inheritance but as yet I am only able to use deep Inheritance with VB.Net. Is it possible to use Multiple Inheritance with VB.Net? or are we VB programmers still just short of the mark?
One thing I have noticed though is that C# allows multiple Inheritance but as yet I am only able to use deep Inheritance with VB.Net. Is it possible to use Multiple Inheritance with VB.Net? or are we VB programmers still just short of the mark?
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
