See Claude's idea for a way around this.

I agonized over this for a few months, but I just show up early (6am) and stop the webserver, copy the DLL, register it and it is done in 5 seconds.

I think it is cheezy to do this. I hope that the foxteam can provide some sort functionality that would allow us to create DLL's as in .NET where you just XCOPY them into the folder, then ASP.NET grabs the new version when it needs it. No stopping of the webserver, no registering the DLL. Lack of this tool will mean that I will slowly migrate away from VFP over the next 2 years.

The upside is the my biz logic doesn't change very often, so I don't have many early mornings.

> My concern with VFP COM was/is is that every time you make a change to the VFP COM you have to re-register it on the web server. Was it every a problem/concern in your work?
>
>
>>Hi Steve. I return XML strings from my VFP COM components, then C# puts this into an ADO.NET dataset and vice versa. Works much faster that I thought it would.
>>
>>>Are you using VFP COM objects? How do you move the data between .NET & VFP? ADO or XML?
>>>
>>>>
>>>>Use both .NET and Foxpro, that is what I do. Use .NET as your UI that calls your FoxPro data and biz rules and reports in your backend. This eases you into .NET.
>>>>
>>>>For Windows app development, I don't see reason to use .NET, but if you have a browser front end, then ASP.NET is the way to go.