To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=96859
                 Issue #|96859
                 Summary|CLI UNO requires .NET Framework 3.5 
               Component|api
                 Version|OOo 3.0
                Platform|Unknown
                     URL|
              OS/Version|Windows, all
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|code
             Assigned to|jsc
             Reported by|rpavelic





------- Additional comments from [EMAIL PROTECTED] Wed Dec  3 17:20:28 +0000 
2008 -------
This is not a bug report, but a complaint, so that you can't say nobody is 
complaining about this.

CLI UNO should support .NET 2.0 and not .NET 3.5.

There is no way for existing applications to continue to use OOo api interface 
anymore with new OOo 3.0. Converting application from .NET 2.0 to .NET 3.5 is 
not an option.

I bet there is not a single feature in new CLI UNO dlls that requires .NET 3.5.

.NET 3.5 is almost 200 MB in download size, while .NET 2.0 is only 20 MB (and 
is part of the windows update).

While Microsoft is improving their MS Office API (almost version independent - 
same dlls works with 2003 and 2007) Sun is downgrading OOo API (now you can't 
even have more than one OOo installed).

Good work guys.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to