Is running LogicApps as dotnet-isolated
a supported feature?
#816
Replies: 2 comments 2 replies
-
transferred to this Q&A Question |
Beta Was this translation helpful? Give feedback.
-
Over at the Q&A Question there has been some activity, recently, which led me to the conclusion that the answer to my original question should be a NO, at least from the perspective of having full control over the apps startup (and to do things like adding TLDR; |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi.
We´re currently developing some line-of-business (LOB) custom-connectors in order to be able to automate various tasks in our business.
One thing we didn´t find anywhere documented / sampled is a way to "hook" into a workflows "lifecycle"-events, such as
started
,ended
(orfailed
, maybe).As there may be other things that´d be good to have finer grained control over, I started to try to host LogicApps (Standard) in a
dotnet-isolated
-mode, following these instructions here.Current hope is that this way we could levereage some
Middleware
to achieve the initial goal, as well as having complete control over the apps start-process, etc. seems like a nice benefit, also.Sadly, I´m facing various issues when trying to get this running. I´ve got the feeling that I´d "just" need to reflect the same startup-configuration which
azure functions core tools
does in order to get LogicApps (Standard) indotnet
-mode up and running, but currently am missing the needed pieces / directions.So:
dotnet-isolated
a supported mode to host LogicApps (Standard) ? If so, are there any directions on how to configure the necessary services, etc. inprogram.cs
?Beta Was this translation helpful? Give feedback.
All reactions