Is there any document, article, draft sample, etc. on how to create my Base SF classes with my custom changes that can be use in all my SF applications?

I am feeling pretty confident with my SF learning and I am ready to start working on a 2nd SF project, but now I figured out that all the code I am using in my first project can not simply be copied over to the new project and I hate to keep repeating code and process when there should be a much better an efficient way to do this.

I would really appreciate if anybody can take some time to describe this subclass process in order to crate a Base set of SF classes.

hmmm, may be that could be an Enhancement Request   Sorry Trent

P.S.

I know this will be part of the upcoming SF trainning class, but I can really wait, I need to start working on the 2nd SF project ASAP.

I don't know what you mean my an enhancement request as this has nothing to do with the framework as much as it does organizing your application.

This is a topic that we cover in the training class and is broader than the scope of this forum.  We have an entire section that we will cover in training.  Sorry, but this is not something that we will go over in depth here on the forum as this requires explanation and, well...training.

Sure I understand your points and that is one of the reasons I signed up for the training.

What I meant with enhancement request is that as you know I am coming from VFP environment, VFP 3rd party Framework vendors includes blank subclasses in their process of creating a new project which help the developer in a way to just add their changes in one of the provided subclasses, in my case with Visual ProMatrix, they have the following classes:

• The VPM class, this is the one with their source code, which they modify all the time.
• A DEV class which is global to all projects
• And a PRO class with is specific to the current project.

So whenever you create a new VPM project a new set of Pro Classes will be created for you, and the DEV classes will always be in a common path folder for all projects.

Due to my lack of knowledge for the .NET environment, I don't know if this is even possible or feasible to do in .NET and more important in SF.

In my case, I have several VFP projects that must be converted to SF, so I need to know how to handle the above situation in order to be more productive, and if there is any starting point kind of document or draft that will help me get started prior to the training, and from anybody in the forum I would really appreciate it.

This is the first time I have ever had a request for this.  Really, once you see how to do this it is there is no need for empty classes.  In fact, many of the assemblies and classes that you create could and should be used accross all of your projects.  They should be re-usable!

Obviously I understand the point of purchasing training and coming to class and we look forward to having you here.  But this is not something that I want to elaborate on here on the forum because this turns into training on the forum, which is not the intent of the forum.  This would basically require me to take the rest of the day, produce docs, samples, etc. just for this one post.  This is not a feasible request.  Sorry

Trust me, you will see more of this coming from us (VFP-Frameworks users), even if they don't make sense in the .NET world.

That sound pretty good.

Trent, don't  worry about it.  I do understand, and it is not my intention to have a training session in the forum, that is why I asked to anybody in the forum that has done this if they have any documentation or quick steps they could share since I am in the process of creating my 2nd SF project and wanted to reuse some of the code I have done.  If nobody comes forward today, I will simply do what I can to advance this project and wait until the class to cleanup my messy code .

Well, keep this in mind...we used FoxPro (and dealt with VFP frameworks) for 17-18 years...so we have a little insight here too...not to say that more great ideas won't come down the pike

I have used VPM and FoxPro and the best advice I can give you is to forget about both when thinking of SF/.NET. In my opinion, .NET is much better at sub-classing objects than FoxPro ever was and SF is far more powerful than VPM. Trying to equate SF/.NET back to VPM/Foxpro thinking, I believe, confuses the issue and doesn't help with the considerable learning curve with .NET. I realise this is a statement that could infuriate many VPM/FoxPro users and that is not my intention.  In fact, I seem to recall being told on the VPM forums to "clear off to my .NET buddies" (or words to that effect) by one VPM user several years ago. Ironically, that very same VPM user is now a member of these forums and expressing regret at not getting into .NET sooner, so it would appear he has followed me which I find most amusing .

In any event, the learning curve with .NET is a long path and there is MUCH to learn. However, it is well worth it. I still have to maintain an old VPM based application from time to time and I absolutely hate having to do it as VPM/Foxpro is so dated and cumbersome in comparison to .NET. SF adds another layer which is light years ahead of VPM.

There should be many references on the web about .NET sub-classing and I do think it isn't really a SF issue. One really nice feature is you can freely change your class hierarchy without having to hack Foxpro files -so it is easy to experiment.

Aaron

Agree, I have done that in order to get into .NET, but there are still some nice functionalities available in those frameworks which could enhance SF more.  Keep in mind that were are not here to talk about which one is the best, obviously there could be not fare comparison between VFP/.NET since they are not look alike technologies.  In my case, I would simply express what I would like to see in the framework I choose to stay with for the years to come.

In my opinion, .NET is much better at sub-classing objects than FoxPro ever was and SF is far more powerful than VPM. Trying to equate SF/.NET back to VPM/Foxpro thinking, I believe, confuses the issue and doesn't help with the considerable learning curve with .NET. I realize this is a statement that could infuriate many VPM/FoxPro users and that is not my intention.  In fact, I seem to recall being told on the VPM forums to "clear off to my .NET buddies" (or words to that effect) by one VPM user several years ago. Ironically, that very same VPM user is now a member of these forums and expressing regret at not getting into .NET sooner, so it would appear he has followed me which I find most amusing .

I also agree with you in the superiority of .NET and again, I am not trying to compare the two, otherwise I would simply stay with VFP/VPM, etc.   I don't know which VPM user you are talking about, but I have seen many discussion in that regard and I simply try to avoid them, it is not worthy.  All this depend on the time and place we are in terms of the new technology.  In my case I got into .NET with VS2005 and with a framework that today and tomorrow will deliver the tools I need to be more productive, and that is why I choose SF instead of IdeaBlade, and that does not means IdeaBlade is bad at all.

Well, I also agree with you .  I am moving to .NET due to conviction and not because a client X requested project X to be done in .NET.  As a private consultant I get to decide which tools to use to deliver my customers solutions, and having a VFP/VPM project at a 65%, I decided to re-start it in .NET and I tried with IdeaBlade and SF, I gave each of them one week and I think you know the outcome .  IdeaBlade even offers free training and has a tons of documentations and videos which help out, but for me SF is more suitable.

Yes, I even have some books that talks about it, but one can get confused from time to time, so there is not better time for the SF Training on July 14th.  Like Trent has said here many times, it is easier than we though.