Deploying .Net components to IIS


Hi PowerSphere.

In old days ( pre Appeon PowerBuilder 2017) it was possible to use the runtime packager to make a .Net runtime package to install on the IIS.

This option in not available anymore. (I guess) 

Is there another solution other than to manually copy the Sybase.PowerBuilder.*.dll to the IIS 's  \assembly\GAC_[MSIL|32|64] 

And can I find some kind of documentation on this ?



Question Tags: 


Chris Pollach answered Deploying .Net components to IIS

Hi Georgios; I'm using the PB 2017 "Packager" utility to install the run-time on to IIS machines successfully. The key is the regular DLL's are in the machines system path & the .Net DLL's get registered in the GAC. To which, the "Packager" produced MSI should do for you. The next key part is that you setup the appropriate Application Pools for your PB web services, enable 32bit execution in the target IIS machine and assign the proper execution rights as well to the application pools. Regards ... Chris

marian_16104's picture

Hi Chris, 

PB 2017 Runtime Packager utility do not have option to generate .PB NET runtime package. All steps you described are valid for PB 12.6 but not for PB 2017. There is actually no other way how to deploy .NET web service target to IIS than manually copy all PB 32 bit runtime dlls and copy all PB .NET dlls to GAC. Evn 32 runtime package generated by PB 2017 Runtime Packager do not include all required files for .NET web service target. Problem is that there is no documentation which files are needed for supported .NET targets, this mean all dlls has to be copied to deployment machine. I believe Runtime Packager should be able generate runtime package for all supported targets (as did on PB 12.6), not just for 32/64 bit windows executable.