Posts related to: .NET
wwDotnetBridge and Loading Native Dependencies for .NET Assemblies
If you're using a .NET component with wwDotnetBridge or plain COM Interop that has a native dependency on non-.NET DLLs, you need to be careful to ensure that the native libraries can be found. In this post I describe how .NET assembly loading works and how external native dependencies are resolved in .NET and subsequently how you have to deal with them in your FoxPro applications.
FoxPro Date Rounding Errors in COM and .NET
FoxPro dates can be finicky when travelling over COM and COM Interop for .NET. Ran into a nasty issue with dates from cursors showing up as slightly rounded date values in .NET which lose some of the document definition. Here's what the problem is and how you can work around it in .NET.
Calling async/await .NET methods with wwDotnetBridge
More and more .NET APIs expose Async only interfaces and it might seem that calling async await code from FoxPro seems like it would be difficult. I had my doubts it would but as it turns out it does. In this post I describe how async await works in .NET and how the lower Task API is used to implement it, and more importantly how we can call async methods using the .NET Task API.
Fixing wwDotnetBridge "Unable to load Clr Instance" Errors
When you get "Unable to load Clr Instance" Errors while trying to load wwDotnetBridge, look for an unfortunate but simple to fix security issue with Windows. Here's how to get around this error.
wwDotnetBridge and .NET Versions
wwDotnetBridge supports explicitly specifying which version of the .NET Runtime is loaded. But only one version of the runtime can be loaded into the FoxPro application process, and so the first wwdotnetbridge load wins. Here's how loading works and how you can ensure you're loading the right version for your application.
SouthwestFox Sessions Slides, Samples and Links
I've posted my session white papers, slides and examples from the Southwest Fox conference last month. My two sessions where FoxPro and .NET Interop related and covered a few new recent developments that have improved the ease with which Interop can be done.
wwDotnetBridge for FoxPro .NET Interop is now Free and Open Source
wwDotnetBridge is a FoxPro library to help with accessing .NET functionality from Visual FoxPro is now free and open source.
Dropping in MetaWeblog Provider into my FoxPro Weblog
For a while I've been slacking on my FoxPro blogging. Part of the reason has been that I'm spoiled - spoiled by using Windows Live Writer on my main Weblog (where I post most of my .NET and general...
Doing .NET COM Interop with FoxPro? You need a .NET Disassembler
If you're doing any sort of Interop with .NET, it's extremely useful to have a .NET disassembly like Reflector, JustDecompile or ILSSpy at hand to let you discover the functionality available in the assemblies you are interacting with in .NET. You can find out full type names required for instantiation, the exact method signatures for methods to call, and easy navigation to follow parameter names to actual type implementations. .NET disassemblers make Interop discovery much easier to work with.