CS SDK 10.5 Development

Luis_Barrera

Accord to CS SDK 10.5 relase note "The modifications you develop in CSIDE on one platform can be deployed in a Content Server installation on any supported operating system."

Can I develop in a Windows environment, and after that deploy it in a Solaris environment?

Mark_Sherry

Yes, in pretty much the same way that you could develop in Windows with Builder and deploy to any supported platform. That is to say:

• On non-Windows platforms, OLLs don't have a suffix, so myOspace.oll would have to be renamed to myOSpace
• Line endings on Windows are CR LF, while on Linux and Solaris they're just LF. You'll need to convert the line endings for at least the .ini files. There are multiple ways to do this: the dos2unix frequently found on *NIX platforms will do the trick. Many fancier text editors also allow you to set the line ending format when saving.
• If your code relies on built-ins that aren't available on all platforms (for example, the ActiveX built-in), it obviously won't work on those other platforms.
• If your code relies on a drop-in or other external library, you need to make sure that each platform's version of the module ships with a version of the library compiled for that platform.
• Non-Windows file systems can be pickier about case. We suggest that you name all resources in the support and html folder with lower-case names, and refer to them consistently in the code the same. This is particularly important for HTML files since .fHTMLFile's value is lower-cased automatically. If you don't have the HTML file lower-cased, CS won't be able to find the file, the server will give you a Server Did Not Respond error, but there will be no stack trace, and you will be confused. I speak from experience here.

These were all things that you needed to take into account when working with Builder, and you can probably find far more comprehensive guides to distributing modules on multiple platforms elsewhere. (It's something I haven't had to concern myself with for 4+ years now.) CSIDE and Builder are both just ways of producing OLLs, which have always been cross-platform (apart from the caveats listed above). CSIDE doesn't provide any magic compatability powers, except that it's now easier to directly develop on Linux if that's where your product is going to be used (in which case the first two items on the list become "Add the .oll extension" and "Run unix2dos" if you're going to be shipping to Windows.)