Integrating to the max...BizTalk Style

  There are probably already lot of posts on the installation of the Oracle client, so this is a small note; Error: If you start visual studio on a machine that hasn’t got the Oracle 32-bit client installed, prepare to face the following error; ‘The following assemblies are installed SDK assemblies but could not be shown in the customize toolkit dialog because they…..’ Solution This is because VS.Net is 32 bit and you only installed the 64-bit Oracle client. Install for your DEVELOPMENT environment both the 32-bit and 64-bit client.   HTH, Sander

If you use the WCF-Oracle adapter to communicate with Oracle Advanced Queing you are in for a treat. We followed the steps suggested in a very good MSDN post . There are however some caveats; Username is case sensitive The generated schemas have a reference to the package, and Database schema, make sure this is consistent throughout the environments The generated schemas are slightly different then what the WCF-Oracle adapter expects in some cases (more on that below) Use a count procedure to determine if there are messages Generated the schemas is done by following the standard ‘Add Generated items’ wizard so that should not be hard to do. When you generate schemas for Oracle they will typically have the targetnamespace: /Package/http://Microsoft.LobServices.OracleDB/2007/03/ <DATABASESCHEMA> /Package/ <PACKAGENAME > Where the <DATABASESCHEMA> could be something like ‘DBOWNER’ and the packagename could be whatever. When you implement thi...