.Net Core CLR

Started by Jbartz, October 29, 2026, 09:39:50 AM

Previous topic - Next topic

Jbartz

Are there any plans to add the ability to use .Net Core CLR functionality similarly to .Net Framework?

td

We did have an extender for .Net Core in beta but it had three problems; it required a bit of hoop jumping to install, MSFT's constant new version releases made it very time consuming to keep up-to-date for both ILC and users, and users showed little interest in it.

Also note that you can perform must  .Net Core tasks using .Net Framework which WIL does support. Even if MSFT does their best to hide that fact.
"No one who sees a peregrine falcon fly can ever forget the beauty and thrill of that flight."
  - Dr. Tom Cade

Jbartz

Thanks for the update. We are just converting our .Net Framework libraries to .Net Core. I think we can get by with just adding COM accessibility. 

Thanks again,
Justin

Jbartz

@TD - Do you know if anyone has successfully used Winbatchs objectCreate to work with .net "core" dlls?  I was able to register the DLL using Regsrv32, but I keep getting this error message from Winbatch: 1261:  COM/CLR: Exception.

To add, I am able to use powershells object create function successfully.

spl

Quote from: Jbartz on November 06, 2026, 01:27:49 PMTo add, I am able to use powershells object create function successfully.

Just a question. How deep do you want to go with .net objects using WB?
Stan - formerly stanl [ex-Pundit]

Jbartz

I might of spoke to soon about Powershell working. It seems that a tlb isn't created. Looks like there is a third party tool called DSCOM on github that resolves this issue. Unfortunately, I work for a large company and getting that approved will take time. But pointing out for others in case they want to try.

@spl - I'm just checking if I'm missing something small. Its not a huge concern as I can create a console app and use RunWait. It just doesn't feel as clean to me.

spl

Quote from: Jbartz on November 09, 2026, 06:14:45 AMI might of spoke to soon about Powershell working. It seems that a tlb isn't created. Looks like there is a third party tool called DSCOM on github that resolves this issue. Unfortunately, I work for a large company and getting that approved will take time. But pointing out for others in case they want to try.

@spl - I'm just checking if I'm missing something small. Its not a huge concern as I can create a console app and use RunWait. It just doesn't feel as clean to me.

Upon reflection my question was incredibly vague. I was thinking about GUI's and 64-bit methods or functions. Jim has done great work integrating C# into WB. I have a basic WB UDF which can handle STD_Out from PS, mainly 5.1 but I tried it with limited success in PS7. I guess the point would be what it would take to fully integrate .net Core into WB as opposed to determining .net Core features that that would improve WB and a way to call them.
Stan - formerly stanl [ex-Pundit]

SMF spam blocked by CleanTalk