How to add resource which will be saved in ./bin instead of ./bin2?

How to add resource which will be saved in ./bin instead of ./bin2?

  
How do we deploy files to the /bin directory instead of the /bin2 dir? We have to deploy two files everytime we deploy an espace. These
files are needed by modules in the IIS-stack, but can not be used directly from the website-general bin directory. Therefore we need a
copy of these files in every /bin dir of every espace. We hoped to add them once in the oml or using an extension..

regards,

Paul van Hoof

Hi Paul,

In version 5.x you can set the target directory for the resource file as follows


Hope this helps you.

Cheers,
André
That's not a solution, because he wants to target the standard "bin" directory.
With your suggestion we can target to every possible directory we can imagine, except "bin".




Hi Joost: It's possible!!! 

Paul: Using André´s explanation, but with a small change, set TargetDirectory to  .\bin instead of bin

Hope this helps you.


Joost: Correction:

Outsystems copy the file to a "pre-staging" directory D:\Program Files\OutSystems\Platform Server\share\YourESpaceName\full\bin but doesnt copy to the "final" directory: D:\Program Files\OutSystems\Platform Server\running\YourESpaceName\bin

So it isn't a solution after all :(
Of course i already tested al these suggested things before posting here... Still very curious if there is a way to do this.
Will alse investigate to see if we can put the modules on another location so they can be found in every 'context'.

regards,

Paul
Hi Paul,

It is a .Net Library? Have you tried GAC? 

Try to register your module/dll on server's GAC (Global Assembly Cache). After this your module should be exposed to an .NET Application on the server. 
More info and How To's » http://en.wikipedia.org/wiki/Global_Assembly_Cache

Best Regards,
Rafael Pereira

.net module to be used in the IIS requesthandling-stack... therefore it needs to be in bin, otherwise you can not register it as module in IIS.

Hi Paul,

No more ideas!
Report the issue directly to Outsystems Support Team support@outsystems.com.
Seems to be a "copy" failure on deployment phase.  

Best Regards,
Rafael Pereira