I have the source zip downloaded from the accounts section. Now what?



I think this was touched on in class, but the actual implementation didn't stick.



I seem to remember there were not a lot of step involved so if someone could walk me through it I'd appreciate it



( feel free to speak slowly using small words as you might for a lovable but not terribly bright child )



Also are there problems when using a beta for which the source has not yet be put in the account downloads?

After searching here I found instructions to simply install the source and build the source project (I assume that means jus the main on - not necessarily the UI wrappers etc) in debug mode ( assuming that means just Build Solutions as I don't see the option for building in debug vs ?release?)



I'm not sure if I am now able to step into SF ... is there a particularly good method call to step into to test ? Is there anything else I need to do at the individual solution level ?? ( not sure what I should expect to be seeing - if I break on the form load and step into I get the same thing as step over. Shouldn't I see the SF code loading the form or does this just indicate the method is a base .net method with no SF code underneath?)

Okay, opened the Source solution and clicked "Start Debugging"   This time when it built I got this error

But afterward when i put a breakpoint on the InitApplication() in Appmain of my app I was able to step in and step through source, so I guess I've answered my question - that's all there is to it. 

Install source using the EXE provided in downloads.

Open solution for source code.

Build ( start debugging - the same thing? )

Now you can step into SF source in your app.

Hi Charles.

[quote]... build the source project (I assume that means jus the main on - not necessarily the UI wrappers etc) in debug mode ( assuming that means just Build Solutions as I don't see the option for building in debug vs ?release?)

Have a look at your VS Build menu, and see if you can find the "Configuration Manager..." option. If not, go to Tools, Options, Projects and Solutions, General and check the "Show advanced build configurations". Then, have a look at it and you will find the Debug/Release configuration option.

Yep, what Ivan said. You just have to build it in Debug mode, and it should put the .dll files out there for you.  "Start Debugging" actually tries to run the project in debug mode which, depending on which solution you had set as the StartUp project, may not work.

From the sounds of it, though, you have it up and going. Good job

Thanks very much, Ivan.  That is exactly what I was missing.  I think it was there by default in VS 2005 as AI remember having seen it when i first started. 

for lurkers, this is the setting

And stepping into the SF source is really the way to go.  I am continually delighted with the debugging tools in the VS IDE ! 

Great, Charles.

It looks like that in the eyes of MS we are now "advanced" users.

Actually I think we were downgraded. In VS 2008 we are back to not getting the build configuration manager unless we ask for it (and know how to ask for it - or how to ask Ivan )

Just to follow up a bit for benefit of lurkers and anyone searching for this later :

Today we wanted to understand exactly what happened when double-clicking on a row in a listview and briinging up an edit dialog ( the thing that piqued the curiosity was trying to understand why explicitly setting the pointer of the listviews BO to the instance on the edit form was necessary when coming to the edit form from a double-click but was not necessary when coming form a button that called the edit() and then showdialogue()

Once we determined the MouseDoubleclick of the listview (and not the doubleclick as we first thought) was the event that was handled, we put a stub method in the calling form

Put a breakpoint on the endsub.  When the break came, the callstack showed the Microfour method which is being inherited

Doubeclick it in the callstack and you're off an running, can then step through a lot of framework code.

Of course, if you are moving through your code and hit a method (rather than an event handler ) you can just step in to get to the SF stuff

Hope this helps somebody else.  A great way to start understanding (and appreciated) what the Microfourians have been up to