Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CmdLets for PowerShellCore - Xrm.Framework.CI.PowerShellCore.Cmdlets #327

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

janis-veinbergs
Copy link

Would you be interested in .NET Core build of CRM365/Xrm.Framework.CI.PowerShell.Cmdlets ?

  1. Copied Xrm.Framework.CI.PowerShell.Cmdlet commands to a .NET 6 project
  2. Using Microsoft.PowerPlatform.Dataverse.Client instead of Xrm core assemblies. Microsoft.PowerPlatform.Dataverse.Client is .NET core compatible. But is only for D365 Online versions and not on-prem
  3. Only few things had to be fixed - namely CrmServiceClient renamed to ServiceClient and there is no OrganizationServiceProxy property - but there are others, for timeout and stuff.

I was able to successfully use Get-XrmSolution -UniqueSolutionName Default -ConnectionString "AuthType=OAuth;Url=https://org.......api.crm4.dynamics.com;Username=;Password=;AppId=51f81489-12ee-4a9e-aaae-a2591f45987d;RedirectUri=app://58145B91-0C36-4500-8554-080854F2AC97;LoginPrompt=Auto" from PowerShell 7 to get a response.

@janis-veinbergs
Copy link
Author

janis-veinbergs commented Jan 12, 2023

Or perhaps whole CRM365\Xrm.Framework.CI.PowerShell.Cmdlets project should be .net core compatible? What are your thoughts, @WaelHamze ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant