Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add-Type doesn't work properly in PowerShell Azure Functions
See original GitHub issueAdd-Type depends on a set of reference assemblies to properly compile C# code. PowerShell language worker currently doesn’t ship the refs folder as what pwsh does.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Add-Type isn't working - PowerShell Forums
Hi, I'm using PowerShell Studio and getting this anoying error. I started the code in ISE and it was working fine but ported...
Read more >Add-Type (Microsoft.PowerShell.Utility)
The Add-Type cmdlet lets you define a Microsoft .NET Core class in your PowerShell session. You can then instantiate objects, by using the...
Read more >Azure function app, Powershell 7.2 dll module install
The right answer is that add the .dll files to the C:\home\site\wwwroot\ and then in the powershell script run it like this. Add-Type...
Read more >Running Powershell in Azure Functions -
In this article I show MSPs how run scheduled powershell scripts across all customers under management using Azure Functions.
Read more >Powershell call dll function. A function ...
In my last post, I described how to use the Add-Type cmdlet to interact with the Windows API; specifically, the CopyFile function in...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@TylerLeonhardt this should be a PowerShell SDK issue. Not just the language worker, any application that host PowerShell will have the same problem.
This issue is fixed.