Easier as a 64-bit native DLL than as a 32-bit (as I recall from some time ago). This may have changed.
_____ Ian Thomas Albert Park, Victoria From: [email protected] [mailto:[email protected]] On Behalf Of Greg Keogh Sent: Saturday, November 14, 2015 2:39 PM To: ozDotNet Subject: Native DLL and Azure deploy Folks, we have an existing product which is currently deployed to hosted Win2008R2 servers and it's composed entirely of the following: 1. A small NoSQL database. 2. A branch of folders and files, possibly thousands of text files ranging in size from 1KB to 200KB. For ancient historical reasons these files are the "database" of the product and they can't sensibly be normalised into an RDB. 3. A httpBasic service. 4. A REST service. 5. A native 64-bit DLL created by Borland XE C++ which is called via Interop from the two services. My upcoming mission is prove this product can be deployed completely into the cloud (probably Azure because I have a developer account). Everything looks like a cinch to deploy to Azure because everything has a direct equivalent ... EXCEPT the native DLL. Does anyone know if this will present some Azure deployment problems because it's not a managed assembly? Security? The native DLL will also have to read Blobs, so I'm hoping there is something in the Azure SDK to allow this. Greg K
