Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Comparisons and Issues
Message
From
17/02/2004 19:52:01
 
 
To
17/02/2004 16:18:32
General information
Forum:
Visual FoxPro
Category:
Visual FoxPro and .NET
Miscellaneous
Thread ID:
00876760
Message ID:
00878154
Views:
29
Nancy,

I've not done .Net for a couple months as I've come into a situation where Java is now the priority.

However, during my studies, I used a book on building an entire C# project. It included building a couple custom controls, such as a numeric only textbox. I could have sworn the example included adding the textbox to the toolbox so it could be dragged and dropped.

PF

>Stephen-
>
>Crap. I've lost 2 replies to you. Once more might do the trick...
>
>>First, there is subclassing. Keep in mind C# is a brand-spanking new language. 100% OOP-oriented (ha). So, you get subclassing, interfaces, all sorts of wonderous things. IOW, anything OOPy Fox does will be doable in VS.NET. However, as is mentioned elsewhere, there are 2000+ classes, so there isn't quite the same need.
>>
>>-> I can see where one would not have to subclass many of the class definitions that currently exist in .NET but ones that I know I would HAVE to subclass would be the form controls. I would need to, just as I do in VFP, create a class library or file that contains form control class definitions derived from the native base. These controls will then have code in place that will be required for all forms in an application. In VFP we have the Save Control As or a quick dialog where we can create a new class and specify a class but I'm finding it difficult (no doubt due to lack of familiarity with what I'm looking at) to perform this. I would then want to be able drag and drop these new subclassed form controls onto my forms.
>
>You can't drag and drop your subclasses. It has been loudly suggested to the VS.NET dev team that they allow us to add our own visual classes to the toolbox, but I don't know whatever happened to the suggestion.
>
>You can, however, create your own class libraries, and then inherit from them. Say, like,
>
this.label1 = new MyLabel();
>Just don't expect VS.NET to feel like the experience in the Fox IDE. FWIW, I do better when I just give myself over to VS.NET when I'm in VS.NET. IOW, I don't try to make it be like Fox. I accept that it's really powerful, there's a way to do whatever it is I need, I just have to figure out how. That's just me, though.

(On an infant's shirt): Already smarter than Bush
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform