Use code instead of the packages

[riatdyl]

Hello,

I would like to use the code instead of the packages, is it possible ?

This request is because I want to use my own activities and remove the existing ones.
And btw I would edit the activities in the packages.

I tried to remove the "usings" from "Startup.cs" and the ".AddHttpActivities", ".AddEmailActivities", etc. but the activities are always there in the Designer.

[sfmskywalker]

That is certainly possible. You could fork the project and make any changes you want.

However, it might be more interesting still to use the packages, since they would include new features and bug fixes. You can still get those by updating your fork of course, but might be less convenient.

When using the packages, you can still add your own activities without changing Elsa itself.

Regarding the ability to not use any of the existing activities, you can make that work too. All you would have to do from your own startup class is call this:

services.AddElsa(elda => elsa.NoCoreActivities())

PS. This is all Elsa 2. For Elsa 1, you would have to fork the project.

[giannik]

Hello,
I tried the steps above and got the following message (missing .css file) when running ElsaDashboad.Samples.Monolith.

Oh I also need to run npm on the following to get it up to here:

cd ..src\dashboards\blazor\ElsaDashboard.Application
npm install
npm run build

[riatdyl]

Hello,

I tried to run npm install and npm run build where you said.

The problem is that the program executes with no error, but I always have the ERR_CONNECTION_RESET.

I tried to launch ElsaDashboard.Samples.AspNetCore.Monolith and ElsaDashboard.Samples.Monolith but there's the same error.

[riatdyl]

Sure. So, since the samples are (currently) provided as part of the Elsa source code, you will have to build the client-side (JS, CSS etc) assets yourself first (you need NodeJS installed for this to work).

So, where do I have to create the client side assets ?

[riatdyl]

Okay I tried to launch the application normally without IIS Express (default) and it works now !

[sfmskywalker]

Just in case anyone else runs into this issue: to ensure static assets are served even when running in IIS Express and/or in an environment that is not Development and the project is not published, apply the following in Program.cs:

.UseStaticWebAssets()

Like so:

Microsoft.Extensions.Hosting.Host.CreateDefaultBuilder(args)
   .ConfigureWebHostDefaults(webBuilder => webBuilder
      .UseStaticWebAssets()
      .UseStartup<Startup>())

See also this documentation.