Hi David, SnapDevelop version 2022 that will released middle of this year will support .NET 6. As far as standard Windows install, the projects you create with SnapDevelop are server side so there should be no need to install .NET 6 to each user's machine.

Armeen

Thanks for the info.



Just so that you know, we always push the boundaries and we are happily developing Dot Net Class DLLs and importing them into PB for Client Server PC deployment. If I can avoid using VS I always will! Quite often the DLLs supplied by 3rd parties have data entities not supported by PB so we just wrap them and change the data entities to fit the problem. Snapdevelop is great for this sort of quick fix.



We have some Dot Net DLLs used in our Hotel Property Management system and these are the ones causing me issues. We have 100s of deployed clients. However, the blame lands squarely with Microsoft in my opinion. Windows comes with Dot Net 4.n by default. So anyone writing with Dot Net 5.n as the target will have the same problem and the installer for Dot Net is always massive!



My main problem is currently with Dot Net SMTP stuff being rejected by MS 365 because of TLS1.2 not being supported in Dot Net SMTP by default. Apparently there are some registry hacks that fix it but it's a pretty appalling state of affairs. I’m also looking at a longer term solution so targeting Dot Net 5 and above (preferably Dot Net6 for LTS) makes sense as I can see that Dot 4.n will die eventually! You know what would be a great help, would be to have some native SMTP commands on PowerScript ;-)



Once again Thanks for putting together some great tools.



David

Thanks for that context. If you have the source code of these .NET DLLs, there is option to compile your .NET Core project as "self-contained", which includes both your application and .NET Core binaries. https://docs.microsoft.com/en-us/dotnet/core/deploying/deploy-with-vs?tabs=vs156