On 09/01/2011 05:22 PM, Gruetzmacher, Dominic wrote: > > We have a license for this product and use it to create Word documents > in our application. We currently have the .NET 2.0 version of your > product and are using it in a containing assembly also built in .NET 2.0. > > In the near future, we plan to target the .NET 4 platform for all of our > libraries. To avoid potential side-by-side issues with the .NET > Framework and to avoid the need to have the .NET 2.0 Framework as a > prerequisite,
XMLmind XSL-FO Converter for the .NET platform requires having at least a .NET 2.0 Framework. This means that if you don't have a .NET 2.0 Framework at all and instead have just a .NET 4.0 Framework[*], XMLmind XSL-FO Converter should work fine[**]. > we would like to obtain a .NET 4-targeted version of your > library. Do you have a .NET 4 Framework version of your library available? > No because to our knowledge, this version is not needed. Please refer to http://msdn.microsoft.com/en-us/library/ff602939.aspx --- The .NET Framework 4 is backward-compatible with applications that were built with the .NET Framework versions 1.1, 2.0, 3.0, and 3.5. In other words, applications and components built with previous versions of the .NET Framework will work on the .NET Framework 4. --- --- [*] Plus "Visual J# 2.0 Redistributable Package-Second Edition" which is always required. You may download it from http://www.xmlmind.com/foconverter/downloadperso.shtml [**] To be frank, we have not yet tested XMLmind XSL-FO Converter against the .NET 4.0 Framework. However everything said in this email has been verified to be true for say the .NET 3.5 Framework. However we suspect that we'll have to do small adjustments in XFC. See http://blogs.windwardreports.com/davidt/2011/02/calling-j-code-from-net-40.html -- XMLmind FO Converter Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xfc-support
