Over on ProFox there has been some minor grumbling about Sedna requiring SP2. I do not think SP2 is required. I can see some of the components requiring VFP 9, but my guess is the components will work fine with SP1 and maybe even the RTM version.
I think the only things required is the .NET 2.0 framework for the NET4COM, Visual Studio for DDEX, SQL Server for the Upsizing Wizard, and Vista for the VistaDialogs. I believe the SP2 requirement on the Web site is one of those things where Microsoft puts the latest version up because it is what they support.
If you think about it, Microsoft did not enhance the core VFP 9 EXE other than to fix bugs (and put some new ones in {g}). Even the new Reporting enhancements in SP2 work in SP1 (something I heard from Colin Nichols at OzFox 2007 if I remember correctly).
The one thing I have not tested is attempting the Sedna install on a machine without SP2. I would be very surprised if the installer checked to see if you have SP2 installed first. If we find out this is the case, I have a workaround to have both SP1 and SP2 on the same machine peacefully.
Yes, the Report*.App components in SP2 will work with SP1 and earlier. But it is worth repeating that things like dynamic effects do impact performance, and specific optimizations were put in SP2 to reduce this as much as possible.
Rick
You are not fully correct.
VistaDialogs and Net4COM need the 3.5 runtimes – VS2008. DDEX needs the 2 runtimes(VS2005). Here also MS has blundered. So we have 3 NET components, 2 requiring 3.5 runtimes and 1 needing ver 2.0 runtimes. How nice.
DDEX is written in CSharp but the other 2 in VB.NET. How nice. Now I need to learn VB.NET and C# to be able to follow the source supplied.
MS should take a leaf out of their so called “managed” platform and manage versions and languages properly.
I posted on the UT about SEDNA.
I am not impressed.
Hi Bernard,
I guess I don’t understand the frustration with multiple languages. I know there seems to be a split in the .NET world with people polarizing to C# or VB, but if Microsoft wrote everything in one or the other then the “favoritism” argument would likely get stronger.
As far as the runtimes go, this is only on the development machine. DDEX is only for developers. The components you distribute are in the latest .NET runtimes. I would not expect Microsoft to develop something that integrates with Visual Studio in the current version anyway.