VFP still runs on all windows versions...but the dotnet framework isn't

[RedLion]

Did I hit the limitations of Visual FoxPro or is there still a solution or workaround?

Visual FoxPro still runs on all Windows versions without any problems but for connecting it to the internet through IIS I use the dotnet framework (4.5.2). Now there are plans to migrate from windows 2008 to windows 2012 R2. But Windows 2012 doesn't support 32 bit versions of the dotnet framwork?!?!

So the question is, is there a way to install / use a 32 bit version of the dotnet framework or a workaround for it?
Or is there a way to call a VFP COM object from a 64 bit C# web application?

Then another part of the Visual FoxPro desktop application is calling a 32 bits c# System.EnterpriseServices.ServicedComponent (Class Library) via the FoxPro CreateObject("MyCSharpLibrary.myClassName").

Is there a way to call a 64 bits dotnet library from Visual FoxPro?

 

[Olaf Doschke]

In very short (it's late): You err.

Server later than 2008 come for 64bit CPUs only, but both the CPUs and the OSes up to today all have x86 subsystems.
And IIS has a 32bit application pool.

Bye, Olaf.