I've been running and recompiling main.prg without a problem and I've got the same configuration! One thing though is that when there's an error, it does seem to grab and hold the fxp for a little while preventing a recompile. However it does eventually let go and allow a recompile. I wish I knew if there was a setting that controls this.
For 2.11 (and 3 if you set it up) the project hook will automatically 'Unload' the application when it is recompiled. However, this only works when the dll is called from ASP. If called from ASP.NET, it's locked again. That's the reason I went to an external main.prg for version 3.
BTW, have you tested debugging in XP yet?

>Claude,
>
>>if the changes are in main.prg or any of the html templates, then nothing
>>is needed other than saving the changes to those files.
>
>Please explain how this is supposed to work, because it doesn't work that way for me. In 2.11, I had to call IISReset to release any external .FXP routines that were called from the main DLL. In AVFP3, I am experiencing the same situation when trying to modify main.prg.
>
>FWIW, this is on XP Pro w/ SP2.
>
>Thanks,
> Dan