Your delegate must be in the same namespace

Your delegate that calls doRefresh must be in the same namespace as the control linked to the customized pane. (This isn’t explicitly stated in the version of the documentation published 08 June 2010, although the converse situation is mentioned in the section, “Invoking methods on the User Control form a Syspro form”.)

Parameter values must be able to become valid VBScript

The value being passed as a parameter to doRefresh must compile as standard VBScript, i.e.:

• if it contains any double quotes, they must be escaped as two double quotes. Even better, on the .Net side, just encode any double quotes as a non-printable character such as CTRL+C, then on the VBScript side, do the reverse.
• if it contains any new lines, they must be removed.

The parameter which becomes the RefreshValue in VBScript CAN be of unlimited length (contrary to what I first wrote here).

Here is some example code for the DotNet side to safely encode double quotes and new lines:

private static string MakeSafeForVBScript(string sourceString)
{
 // The VB Script will essentially do a statement like this:
 // Dim RefreshValue : Refreshvalue = "<?xml version="1.0" encoding="Windows-1252"?>
 // However, it will give a syntax error on any embedded double quotes or new lines,
 // so convert new lines into CTRL+B,
 // and convert double-quotes into CTRL+D.

 string newLineReplacement = ((char)0x2).ToString(); // CTRL+B
 const char doubleQuoteReplacement = (char)0x4; // CTRL+D
 const char doubleQuote = '"';

sourceString = sourceString.Replace(doubleQuote, doubleQuoteReplacement).Replace("\r\n", newLineReplacement);

 return dotNetVariable;

}

Here is an example VBScript code snippet; it puts the double-quotes and new lines back:

Function Unencode (encodedString)
 Dim control_B
 Dim control_D
 Dim doubleQuote
 Dim newLine
 Dim result

 control_B = Chr(2)
 control_D = Chr(4)
 doubleQuote = Chr(34)
 newLine = chr(13) & chr(10) ' \r\n, i.e. CTRL+M CTRL+J.
 encodedString = Replace(encodedString, control_D, doubleQuote)

 Unencode = Replace(encodedString, control_B, newLine)

End Function

GetApplicationInfo and GetSysproInfo don’t always return pure XML

Note that returned XML from GetApplicationInfo or GetSysproInfo does NOT always contain valid XML, because it sometimes contains embedded double quotes, so you have to  escape those quotes before passing the returned value into an XML parser.

E.g. the returned XML may contain a fragment like this:

<DiagnosticAppPath Value="""C:\SYSPRO61\BASE\IMPACT.EXE"""/>

This needs to become (note the backslashed quotes):

<DiagnosticAppPath Value="\"C:\SYSPRO61\BASE\IMPACT.EXE\""/>

You can use the following C# code to sort out the embedded quotes:

String tripleQuotes = @"""""""";
String singleQuoteBackslashedQuote = @"""";
var fixedQuotes = systemVariables.Replace(tripleQuotes, singleQuoteBackslashedQuote);

Remove XML NameSpace declarations

Also note that Syspro’s Business Objects called from Syspro’s VBScript doesn’t like XML that has namespace declarations; see How to use XSD2Code for Syspro Business Objects for more details. (Calls to Syspro’s Business Objects via Web Services or DCOM don’t seem to have this problem.)

Conclusion

After sorting these things out, you should be ready to run.

There are a number of ways you can resolve this:

• Install your additional assemblies in the GAC.
• Copy your additional assemblies to your SYSPRO/BASE folder (but leave your initial assembly in the SYSPRO/BASE/ManagedAssemblies folder); see this post in the Syspro Forum for more details.
• Combine your assemblies into one assembly using ILMERGE, which you can download from Microsoft here.
  You can edit your .Net project’s properties and create a PostBuild event such as this:

"C:\Program Files (x86)\Microsoft\ILMerge\ILMerge.exe" /v4 $(TargetFileName) MySecondaryDLL.dll /out:$(ProjectDir)$(OutDir)..\$(TargetFileName)

E.g. if you want to download and install Microsoft’s SOAP Toolkit 3 redistributable, which is in MSM format, you can use this procedure. However, for more notes about SOAP, see my related post here.

These instructions are for Visual Studio 2008.

Go to File / New / Project and create a new Setup Project; see the first screen shot below.

Edit the project’s Properties and set your Company name and product name.

Add a new Project, a Merge Module project.

Select the MSM files you want installed.

Build and run.

Check that your MSM files appear where they should, e.g. for Microsoft SOAP libaries, check that they appear in C:\Program Files\Common Files\MSSoap\Binaries.

One example of where you might use this information is where you are writing code in VBA in Excel to talk to a SOAP client such as a Syspro web service that is using SOAP.

SOAP doesn’t work on Windows 2008 R2 Server

Firstly, I found that the Microsoft SOAP libraries still work on Windows XP, Windows 7 (both 32 and 64-bit), but NOT on Windows Server 2008 R2.

They don’t seem to work on Windows Server 2008 R2 because the system can’t find the SOAP DLL’s in the registry, because the system seems to use new, different, or wrong registry keys to locate the SOAP DLL’s:

On Windows Server 2008 R2, the system looked, unsuccessfully, for this registry key:

HKCR\Wow6432Node\CLSID\{the-GUID}\InprocHandler

but on Windows 7 64-bit, where it was successful, it looks for this registry key:

HKCR\Wow6432Node\CLSID\{the-GUID}\InprocServer32.

(This was discovered using Process Monitor to watch registry activity.

How to use SOAP on Windows Server 2008 R2

One solution to accessing SOAP is to create a .Net SOAP client (create a project, add a web service to your SOAP endpoint; add a subroutine to call that SOAP endpoint). Then expose that as a COM object so that you can consume your newly created DLL in VBA or where-ever you want.

NOTE for developers

Visual Studio 2010 must be run As Administrator so that you can test the DLL when you run it from Visual Studio as the SoapClient is exposed as a COM Object and needs to be registered when it is built so that it can be found when it is run.

(You can also manually register it using regasm; again you must run as Administrator.)

On the client’s machine, it doesn’t matter where you put the DLL on the client’s machine but the DLL must be registered using regasm.

The advantage of using a C# object rather than coding your XML as one big string is you get the advantages including:

• Intellisense in Visual Studio – it shows you descriptions about each XML element from the XSD file’s annotations
• Type safety
• Easier to code: you don’t have to convert your types to strings, nor worry about maximum lengths etc. – it’s all done for you.

( I also tried using Microsoft’s XSD.exe tool, but found XSD2Code to be far superior – it is more configurable and so can be made to fit Syspro.)

These instructions are written for XSD2Code version 3.4 with Visual Studio 2010 and Syspro 6.1.

1. Download and install XSD2Code. It integrates naturally with Visual Studio.
2. From the <Syspro installation directory>/BASE/SCHEMAS directory,  add the XSD files for your desired business object into your project. E.g. to call the SORTOI business object, add C:\Syspro61\Base\Schemas\SORTOI.XSD and SORTOIDOC.XSD into your Visual Studio Project. Actually, I prefer to copy the XSD files into the appropriate sub-directory of my Visual Studio project and then add them from there, so that I can put the XSD files under source code control. (I use Mercurial.)
3. In the Visual Studio Solution Explorer, right-click on the new XSD file and select Run XSD2Code Generation.
4. Set the following parameters; the rest can stay as their default values. This is the key bit:
   1. PropertyParams/GeneratePropertyNameSpecified must be None, otherwise you won’t get parameters generated unless you set the corresponding fieldSpecified to true.
   2. Set the Code/NameSpace to <your-namespace> + the XSD name, so that there aren’t clashes with other XSD’s that use the same internal variables. E.g. I set mine to Syspro.Base.Schema.SORTOI and Syspro.Base.Schema.SORTOIDOC.
   3. Set the Code/TargetFramework to Silverlight or Net40 as appropriate.
   4. Leave the Serialization/DefaultEncoder as UTF-8.
   5. Set Serialization / Enabled to True. This saves you having to write your own serialization routine.
   6. Set Serialization / Generate XML Attributes to True.
5. Press the Generate button.

Group your files

In the Visual Studio Solution Explorer, to have the newly generated .cs file (e.g. SORTOI.designer.cs) grouped under the XSD file (e.g. SORTOI.XSD), i.e. as a branch UNDER the XSD file instead of as a sibling file, follow these instructions:

1. Close Visual Studio.
2. Edit the .csproj file for that project with a text editor (such as vim or Notepad).
3. Add DependentUpon tags (and open and close the Compile tag).
   E.g. change this line:
   <Compile Include=”Schema\SORTOI.designer.cs” />to this:<Compile Include=”Schema\SORTOI.designer.cs”>
   <DependentUpon>SORTOI.XSD</DependentUpon>
   </Compile>

Generate your XML

Now you can create code your XML settings using plain old C# objects as simply as this example:

var SORTOI_Parameters = new SORTOI.PostOrders()
{
 Parameters = new SORTOI.Parameters()
 {
     ValidateOnly = PORTOI.ValidateOnly.Y,
     StatusInProcess = PORTOI.StatusInProcess.N
 }
};

Serialize your objects

To convert your object to XML, you can use code such as this:

string XmlParameters = SORTOI_Parameters.Serialize();

Syspro’s VBScript doesn’t like namespace declarations

Note that if you use a different method to serialize your code, you may end up with XML Namespace declarations in your XML like this:

<Orders xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xmlns:xsd=""http://www.w3.org/2001/XMLSchema""">

This shouldn’t be a problem BUT if you are passing this XML to Syspro’s VBScript and then calling a Business Object from VBScript, it will not like the xmlns declaration, so you may want to add this code on the VBSCript side (see related article, How to invoke a Syspro VBScript function from a .Net User Control):

Dim nameSpaceDeclaration
nameSpaceDeclaration = "xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xmlns:xsd=""http://www.w3.org/2001/XMLSchema"""
XmlParameters = Replace(XmlParameters, nameSpaceDeclaration,"")

This was the case for Syspro 6.1 Port 69.

Adjust the encoding for Silverlight

If you are using this in Silverlight, you may need to adjust the XML encoding; this is an ugly way of doing it:

XmlParameters = XmlParameters.Replace("encoding=\"utf-8\"", "encoding=\"Windows-1252\"");

A better way of doing this may be to set XSD2CODE’s parameter, Serialization/Enable Encoding to True, and then pass the Serialize routine a parameter to select which encoding to use; I have yet to try this.

Then you can pass those XML strings to the web service for the business object, e.g:

setupProxySORTOI.AddAsync(userId, "SORTOI", XMLParameters, XMLIn);

1. Create an account for yourself on LaunchPad.
2. Upload your ssh signature as per https://help.launchpad.net/YourAccount/CreatingAnSSHKeyPair
3. Log in to Launchpad: On Centos:

   bzr launchpad-login <your-launchpad-login>

   On Ubuntu:

   bzr whoami <your-launchpad-login>

4. Get the latest trunk source code: For the server:

   bzr branch lp:~openerp/openobject-server/trunk

   For the modules:

   bzr branch lp:openobject-addons

5. To update (cf. svn update, i.e. freshen) your branch later:

   bzr pull

How to contribute your changes to the OpenERP Community

1. Join the OpenERP Community here: https://launchpad.net/~openerp-community
2. You should probably create a bug or mod with a Blueprint on Launchpad in the appropriate project.
3. Make your changes.

   vi addons/account/account.py

4. Commit to your local branch.

   cd addons
   bzr ci -m "Testing Modifications"

5. Push your changes up to Launchpad.

   cd addons
   bzr push lp:~openerp-community/openobject-addons/YOURLOGIN_YOURBRANCHNAME

   Don’t forget to set the status of your branch (new, experimental, development, mature, …) so that contributors know what they can use or not.

6. Bind your local branch to the one on Launchpad so that future commits will be applied directly to the one on Launchpad.

   bzr bind lp:~openerp-community/openobject-addons/YOURLOGIN_YOURBRANCHNAME

7. Further editing would then follow these steps:

   bzr pull    # Get modifications on your branch from others
   EDIT STUFF
   bzr ci    # commit your changes on your public branch
   OR
   bzr ci --fixes=lp:453123   # Where 453123 is a bug ID

8. Update your branch from its parent branch:

   bzr merge

9. Once your branch is mature, mark it as mature in the web interface of launchpad and request for merging in the official release. Your branch will be reviewed by a commiter and then the quality team to be merged in the official release.

More Information

• You can find the main OpenERP projects from this page: https://launchpad.net/openobject
• You can find more about OpenERP’s development process here: http://doc.openerp.com/v5.0/developer/1_1_Introduction/2_launchpad.html

Filed under: OpenERP ]]> http://powerphil.wordpress.com/2012/02/08/guide-to-using-launchpad-for-openerp-development/feed/ 0 philubert http://powerphil.wordpress.com/2012/02/08/how-to-install-and-use-eclipse-for-python-development-and-debugging-with-openerp/ http://powerphil.wordpress.com/2012/02/08/how-to-install-and-use-eclipse-for-python-development-and-debugging-with-openerp/#comments Wed, 08 Feb 2012 10:03:19 +0000 philu http://powerphil.wordpress.com/?p=102 Continue reading →]]>

How to install Eclipse on Windows

• Download and install the Java SE JDK
• Download and install Eclipse Classic 3.5.1 or later from http://eclipse.org
• In Eclipse, install PyDev by going to Help / Install new software / Add.
  • Name: Pydev
  • Location: pydev.org/updates.
  • Then tick PyDev, Next, Install PyDev for Eclipse.
  • After it has installed, go to Windows / Preference / Pydev / Interpreter – Python; go to Python Interpreters.
  • Click the “Auto Config” button. It should list a lot of directories. Make sure you tick the directory for PyDev; it is probably the first or last directory in the list, and probably the only one not yet ticked.

• Install the GUI Desktop, e.g.:

  # yum groupinstall 'X Window System'
  # yum groupinstall 'Gnome Desktop environment'

• Install Java:

  # yum install java

• Install Eclipse:

  # yum install eclipse-platform

• Run Eclipse in the GUI environment.

  # init 5

• Go to Help / Updates / Find and Install…; select Search for new features to install.
• Click on New Remote Site.
  • Name: Pydev
  • Location: pydev.org/updates.
• Hit Finish.
• Expand PyDev. Select PyDev; you do not need to select ‘PyDev Mylyn Integration’.
• Hit Finish; it should download and install PyDev.
• After it has installed, go to Windows / Preference / Pydev / Interpreter – Python; go to Python Interpreters.
• Click the “Auto Config” button. It should list a lot of directories. Make sure you tick the directory for PyDev; it is probably the first or last directory in the list, and probably the only one not yet ticked.

If you are logged into a graphical desktop, you can debug OpenERP using the following procedure:

• Copy ~openerp/.openerp_serverrc to your home directory.
• Edit /<your-home-directory>/.openerp_serverrc; change the entries for root_path and addons_path as appropriate, e.g.:
  • root_path = /<your-home-directory>/eclipse.workspace/OpenERP/src
  • addons_path = /<your-home-directory>/eclipse.workspace/OpenERP/src/addons
  • Create a new project in Eclipse.
  • Copy all the OpenERP source into the src directory of the project, including all the sub-directories.
  • It is easier if you start Eclipse in the directory where your project lives. There may be a better way to do this, but you could:
    • Stop Eclipse
    • Create a shell script, called something such as start_eclipse, in your PATH with contents like this:

      #!/bin/sh
      cd $HOME/work/eclipse.workspace/OpenERP/src
      exec eclipse

    • Then run start_eclipse from your command-line (or tell XMing to run it).
    • Add all the modules and code to the project:
      • Right-click on the src directory in the PyDev Package Explorer.
      • Go to New / File / Advanced and tick Link to file in the file system.
      • Click on Browse and add openerp-server.py.
      • Do the same for all the other *.py files in the source directory.
      • Click on the src directory in the PyDev Package Explorer.
      • Go to New / Folder / Advanced and tick Link to folder in the file system.
      • Click on Browse and add the addons directory.
      • Do the same for all the other directories.
    • In the top right, select the Debug perspective.
    • Setup a Debug configuration in Eclipse:
      • In Eclipse, go to Run / Debug….
      • Select Python Run.
      • Click the New button.
      • Give the configuration a Name.
      • Select your OpenERP project.
      • For Main Module, browse to openerp-server.py
      • On the Arguments tab, add start-up arguments that you may want; see /etc/init.d/openerp-server for arguments.
        E.g. you may use: –logfile=/var/log/openerp-server.log –log-level=debug.
      • Apply the changes and Close.
    • Set breakpoints in your source files as desired.
    • To start debugging, press the Debug toolbar icon or go to Run/Debug… and press the Debug button.

To turn your Linux’s installation of Eclipse from your Windows PC, download and install the XMing server. This actually works quite well – the responsiveness is better than running a Gnome desktop inside a Virtual Machine. Run Xlaunch and tell it to run eclipse or your start_eclipse shell script in a multi-window environment.

Download and install code snippets from: http://code.google.com/p/openerp-eclipse-template/

Code snippets are shortcuts for adding template code.

If you create a file in Eclipse, the Windows version, and it saves in DOS format (as opposed to Unix format end-of-lines), then OpenERP 5 will not detect or load the module. You can use Unix’s file command to tell you which files have these unwanted CRLF’s:

E.g. these files had problems (note the CRLF line terminators notes):

/home/phil/openerp/addons/my_product_kit # file *.py *.xml
__init__.py:              ASCII Java program text, with CRLF line terminators
my_product_kit.py:        ASCII Java program text, with CRLF line terminators

but these did not:

/home/phil/openerp/addons/my_product_kit # file works/*
works/__init__.py:         ASCII English text
works/my_territory.py:     ASCII Java program text
works/my_territory.xml:    ASCII text
works/__terp__.py:         ASCII text

# service smb start
# smbpasswd -a philu
# setsebool -P samba_enable_home_dirs
# setsebool -P samba_export_all_rw on
# chcon -R -t samba_share_t /home/philu

• https://answers.launchpad.net/openobject-addons/+question/104901
• http://www.openerp.com/forum/topic6334.html
• http://boiciuc.blogspot.com/2011/03/openerp-remote-debuging-on-server.html

OpenERP configuration files on Centos 5.5

• /etc/openerp-web.cfg
• /etc/init.d/openerp-web
• /etc/init.d/openerp-server
• ~openerp/.openerp_serverrc – for the OpenERP Server
• ~/.openerp_serverrc – if running an OpenERP Server inside Eclipse from your own userid
• /usr/lib/python2.4/site-packages/openerp-server/tools/config.py – for default values if no config file

• /etc/openerp-web.cfg
• /etc/init.d/openerp-web
• /etc/init.d/openerp-server
• ~openerp/.openerp_serverrc – for the OpenERP Server
• ~/.openerp_serverrc – if running an OpenERP Server inside Eclipse from your own userid
• /usr/local/lib/python2.6/dist-packages/openerp-server/tools/config.py – for default values if no config file

• C:\Program Files (x86)\OpenERP AllInOne\Server\openerp-server.conf
• C:\Users\<Your login>\.openerprc

• /var/lib/pgsql/data/postgresql.conf
• /var/lib/pgsql/data/pg_hba.conf

• /etc/postgresql/8.4/main/pg_hba.conf
• /etc/postgresql/8.4/main/postgresql.conf

• C:\Program Files (x86)\OpenERP AllInOne\PostgreSQL\data\postgresql.conf
• C:\Program Files (x86)\OpenERP AllInOne\PostgreSQL\data\pg_hba.conf
• C:\Program Files (x86)\OpenERP AllInOne\PostgreSQL\data\pg_indent.conf

OpenERP Server logging

Server Log files on Centos 5.5

• /var/log/openerp-web
• /var/log/messages (if –syslog option is used to start the openerp server – see /etc/init.d/openerp-server)
• /var/log/openerp-server (if that is where you pointed your log file to in /etc/init.d/openerp-server)
• ~openerp/.bzr.log

Client Log files

For the GTK Client on Windows 7:

• C:\Users\<Your login>\openerp-client.log

Postgres Logging on Centos 5.5

• /var/lib/pgsql/pgstartup.log (see PGLOG in /etc/init.d/postgresql)
• /var/lib/pgsql/data/pg_log/postgresql-*.log (see /var/lib/pgsql/data/postgresql.conf)
• C:\Program Files (x86)\OpenERP AllInOne\PostgreSQL\data\pg_log

Postgres Logging on Ubuntu 10.10

• /var/log/postgresql/postgresql-8.4-main.log

I successfully retrieved all my email (and account) by doing this:

1. Closed Windows Live Email.
2. Made a backup copy of C:\Users\Philu\AppData\Local\Microsoft\Windows Live Mail and also of C:\Users\Philu\AppData\Local\Microsoft\Windows Mail (not sure if that second directory is needed but I did it too, just to be safe).
3. Made a System Restore Point.
4. Downloaded and installed ShadowExplorer.
5. Selected the most recent time in the Toolbar button.
6. In the navigation pane, navigated to C:\Users\Philu\AppData\Local\Microsoft.
7. Right-clicked on Windows Live Mail and exported it to a temporary directory.
8. Did the same for the Windows Mail directory.
9. Closed ShadowExplorer.
10. Opened Windows Explorer.
11. Cut C:\Users\Philu\AppData\Local\Microsoft\Windows Live Mail and also C:\Users\Philu\AppData\Local\Microsoft\Windows Mail and pasted them into another backup directory.
12. Moved my exported copies of Windows Live Mail and Windows Mail from steps 7 and 8 into C:\Users\Philu\AppData\Local\Microsoft.
13. Opened Windows Live Mail.
    All my mail was back!

I was using Windows 7 Home Premium (64-bit) with Windows Live Email Version 2011.

Edit: Simon van der Pol kindly posted an easier method for Windows 7 users:

1. Close Windows Live Mail.
2. Go to C:\Users\username\AppData\Local\Microsoft and then right click on the Windows Live Mail folder and choose ‘restore previous versions’.
3. Then choose the most recent date to restore to and click restore.
4. After restoring to a previous date, you can always restore back to a future date.
5. Then open Windows Live Mail. All your e-mails should be in place.

References

• http://www.eggheadcafe.com/software/aspnet/36211882/deleted-email-account.aspx
• http://www.shadowexplorer.com/