semantic-kernel icon indicating copy to clipboard operation
semantic-kernel copied to clipboard

.Net: Bug: ProcessBuilder cannot be found

Open ThimoDEV opened this issue 8 months ago • 7 comments

Describe the bug After installing Semantic Kernel and SemanticKernel.Process.LocalRuntime The ProcessBuilder type cannot be found

To Reproduce Steps to reproduce the behavior:

  1. Create newC# project
  2. Install SemanticKernel 1.46 and SemanticKernel.Process.LocalRuntime 1.46 alpha
  3. Create a method and try to make a ProcessBuilder
  4. See ProcessBuilder cannot be found

Expected behavior I expect when I follow the Process Framework example docs that the objects are in the SemanticKernel.Process.LocalRuntime package

Screenshots If applicable, add screenshots to help explain your problem.

Platform

  • Language: C#
  • Source: SemanticKernel.Process.LocalRuntime 1.46 alpha
  • AI model: --
  • IDE: Visual Studio
  • OS: Windows 11

Additional context Add any other context about the problem here.

ThimoDEV avatar Apr 15 '25 10:04 ThimoDEV

Hi @ThimoDEV we have a getting started sample here https://github.com/markwallace-microsoft/semantic-kernel/tree/main/dotnet/samples/GettingStartedWithProcesses

You can modify this to use the release packages locally. Can you compare this to what you are doing?

markwallace-microsoft avatar Apr 15 '25 11:04 markwallace-microsoft

Hi @markwallace-microsoft ,

I used the latest stable version of the Microsoft.SemanticKernel nuget package which doesnt have the ProcessBuilder class. However Process Framework requires me to use the Microsoft.SemanticKernel.Core 1.46 alpha version to make it all compatible. This is not yet documented that thats the case.

So now with the Core alpha version it can find the ProcessBuilder class.

Having the terminal add package command for the core package under the Process.LocalRuntime in the docs would help a lot

ThimoDEV avatar Apr 15 '25 12:04 ThimoDEV

Have you tried adding these packages:

    <PackageReference Include="Microsoft.SemanticKernel.Process.Abstractions" Version="1.47.0-alpha" />
    <PackageReference Include="Microsoft.SemanticKernel.Process.Core" Version="1.47.0-alpha" />
    <PackageReference Include="Microsoft.SemanticKernel.Process.LocalRuntime" Version="1.47.0-alpha" />

davidpene avatar Apr 25 '25 09:04 davidpene

Have you tried adding these packages:

    <PackageReference Include="Microsoft.SemanticKernel.Process.Abstractions" Version="1.47.0-alpha" />
    <PackageReference Include="Microsoft.SemanticKernel.Process.Core" Version="1.47.0-alpha" />
    <PackageReference Include="Microsoft.SemanticKernel.Process.LocalRuntime" Version="1.47.0-alpha" />

Yes, but that wasn't specified in the docs

ThimoDEV avatar Apr 25 '25 11:04 ThimoDEV

So now with the Core alpha version it can find the ProcessBuilder class. Having the terminal add package command for the core package under the Process.LocalRuntime in the docs would help a lot

Re-read this 👍 Agree having this in the docs would save devs the headache.

davidpene avatar Apr 25 '25 23:04 davidpene

@ThimoDEV when you build your code with these packages via Github actions, does it timeout on ubuntu-latest? It only works for me with at least an 8-core machine.

@markwallace-microsoft / @alliscode have you had anyone else experience this? Looking through all the *.props references but nothing seems to be immediately obvious.

davidpene avatar Apr 26 '25 06:04 davidpene

@ThimoDEV when you build your code with these packages via Github actions, does it timeout on ubuntu-latest? It only works for me with at least an 8-core machine.

@markwallace-microsoft / @alliscode have you had anyone else experience this? Looking through all the *.props references but nothing seems to be immediately obvious.

To be fair I haven't continued using Process Framework. I need to built a C# version of langgraph and I had to go with a custom engine as right now I couldn't fit Process framework into it

ThimoDEV avatar Apr 26 '25 08:04 ThimoDEV