You can copy your compiled assembly in a subfolder in your pb application and then make your pb generated object see it using a relative path.

AppFolder/MyAssembly/<here put your assembly>.

Then change is_assemblypath to ./AppFolder/MyAssembly/<your assembly.dll>. Don't forget to add . before /AppFolder...

Another way is to GetCurrentDirectory when your application starts and hold it's returned value to a global variable. In this case is_assemblypath should get as value <apppath global variable>/AppFolder/MyAssembly/<your assembly.dll>.

Andreas.

Question : String is_assemblypath is sets the path where the machine is creating the build. How to make this path dynamic ?

eg: In Build machine path is like D:user/task/app_source

is_assemblypath = "D:user/task/app_source"

My deployment machine have the exe in D:/app_1

Just make sure you are aware that PB has HTTP client, JSON parser/generator, OAuth and JWT token support, etc. so there is no need to use a .NET DLL you can natively call virtually any Web service from PB directly.  By doing so you make your deployment configuration and dependecy simpler and avoid the kind of problems you are having. 

Hi.

I guess that your generated object contains a full path defined for your assembly. Edit source the generated object and search for "String is_assemblypath" and check if it's value is a full path. If this is the case change it to a relative path (and place your assembly to the appropriate location).

Also, for deployments to end user pc's you need to deploy some additional runtime files. Check the documentation.

Andreas.