To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=100071
User jl changed the following:
What |Old value |New value
================================================================================
Ever confirmed| |1
--------------------------------------------------------------------------------
Status|UNCONFIRMED |STARTED
--------------------------------------------------------------------------------
Priority|P2 |P3
--------------------------------------------------------------------------------
Target milestone|--- |OOo 3.2
--------------------------------------------------------------------------------
------- Additional comments from [email protected] Thu Mar 12 12:06:34 +0000
2009 -------
I updated the Wiki at
http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/ProUNO/CLI/Writing_Client_Programs
What you need to to is open a socket from your client program, for example:
System.Net.Sockets.Socket s = new
Syste.Net.Sockets.Socket(AddressFamily.InterNetwork, SocketType.Raw,
ProtocolType.IP);
This is a work around to initialize the windows socket API.
Then provide an ini file, which is named as your client program (without
extension). For example: client.exe -> client.ini
It must contain:
[Bootstrap]
URE_BOOTSTRAP=file:///d:/OpenOffice.org%203/program/fundamental.ini
Adapt the file URL to your local office installation.
@myself: Check if cli_cppuhelper should/can call WSAStartup.
---------------------------------------------------------------------
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]
