.NET Web Services and Visual FoxPro COM Object Threading Issues

Posted by: Rick Strahls WebLog, on 21 Nov 2006 | View original

One good reason to use .NET with Visual FoxPro is to publish Web Services. Since the SOAP Toolkit is severely limited in what types of services it can publish using .NET to handle exporting of services is fairly straight forward to do and many developers have surely gone that route.   But what you might not be aware of is that theres a serious issue with Web Services when used with Visual FoxPro in that .NET Web Services run in Multithreaded Apartments (MTA) which means that they are running...

Advertisement
The leading UI suite for ASP.NET - Telerik radControls
Outstanding performance. Full ASP.NET AJAX support. Nearly codeless development.

Similar Posts

  • Improved Lightbox2 JS for Community Server more
  • Deployments made easy more
  • Add-in Comparison: VSFileFinder 2005 vs. SonicFileFinder more
  • Sharepoint 2007 & ASP.NET 2.0 WebParts more
  • This blog is now closed. Please update your links. more
  • Blogging from Tech Ed 2006 - Stefan Shakow on ASP.NET - level 400 more
  • Functional Programming via Anonymous Delegates and Script# more
  • Calling web services hosted outside of your application with Atlas more
  • Introducing CaptainHook - A Subversion Hook Framework For .NET more
  • Passing Arrays between FoxPro and .NET with COM Interop more

News Categories

.NET | ADO.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Community Server | dasBlog | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD