@Chris, Yes, was aware of that and have been using that for other items just was trying to avoid the big hit,

Armeen Mazda @Appeon and Miguel Leeuwe ; The self contained option did work in that it created a published version with a 58mb footprint.

Seems like I have lots of new options so thanks for all the suggestions folks,

Correct me if I am wrong but from what I could determine I had to edit the .pubxml settings file directly to set the <SelfContained>True</SelfContained> but then appears that it did 'publish' it in a self-contained fashion.  Is that the correct way to enable that option?

Still seemed like too much 'plumbing' was included so I tried throwing in the <PublishTrimmed>true</PublishTrimmed> into the .pubxml settings file.

https://learn.microsoft.com/en-us/dotnet/core/deploying/trimming/trim-self-contained

But that really didnt seem to work at all, Either SnapDevelop is not picking that up or it was but wasnt performing the trimming or there wasnt anything else to trim?  

Following up more information on your snapDevelop 2021 publishing documentation I could not determine where any log files from the publishing process were sent to, any ideas?

https://docs.appeon.com/snapdevelop2021/Publish/index.html

Jury is out if the self-published version actually works, illl post a update later if it worked out and deploys without the big .net sdk install or not ..
Another option is to refactor the code into an ActiveX which I am sure would downsize it into a mini footprint, but thats a different can of beans. 

Thanks for all your help,  And yeah, I never sleep ;)

Joseph

I will look at this and see what if I can do a lean trim side by side install and see if that works.

I am trying to deliver a small c# dll from SnapDevelop that seems like overkill to deploy it,

Perhaps I should look at just using C++ and be done with it, I know the VC++ redist is very small compared to the 208mb bloatware .net is trying to make me push out.

For context, this is my PB Code snippet, and the C# dll is nothing more than a small SQL server locator dll nothing too complicated at all, finds all the SQL servers available to the server if the SQL Browser Services are on and pulls the list of catalogs from them based on the uid/pwd per server. Nothing fancy at all, but needing to deliver it with a TRUCK seems like overkill.

PowerBuilder Code Snippet:

DotNetAssembly lnv_assembly
lnv_assembly = Create DotNetAssembly
ll_status = lnv_assembly.LoadWithDotNetCore(This.is_AssemblyPath)

Joseph,

Hi,

See https://learn.microsoft.com/en-us/dotnet/core/deploying/deploy-with-cli 

You can create a "self-contained-deployment". This will give you all the files you need. You can then include those files as external files.

regards.

Hi Joseph;

   There is a "Preload" event in the PC project. With that, you can fire up an external job (ie: .bat file) that checks for the .Net framework version that your expecting. If not found, it could run the .Net runtime install. After that, control would continue on with the PC App startup. Food for thought. HTH

Regards .... Chris 

It’s all up to you to install anything extra your app needs.  PowerClient takes care of PB runtime files, your app EXE and PBDs, and whatever you put in external files tab.  There is also a preload event in project object you can use to execute batch script.