How to find activities being used from a dependency?

Help Studio
, , , , ,
1

Hi,

While trying to convert Windows-Legacy project/template to Windows based project/template, I see there are a list of dependencies that are no longer available in windows based versions.

Hence, there is a need to find alternative ways to handle the activities performed by current dependencies.

However, I don’t want to go through the whole project and find which activity belongs to which dependency.
Neither do I directly want to remove the dependency and then go for resolving all the activities that are shown as errored out post dependency deletion.

What I am looking for is a way to find what all activities have been used from a particular dependency so I can just go to those places, seek an alternate solution first and then go ahead with resolving.

PS: This post was triggered by a need to find replacement for Microsoft.Activities package v 1.0.1 in our windows-legacy projects so these can be converted to windows version.

Regards
Sonali

2

There isn’t a way to avoid just redoing the activities that are missing. If you just press CTRL+S then Studio will give you the “missing activities” prompt and you click OK and it takes you to the first one. You don’t have to find what belongs to what. Just delete the broken activity and re-add it from the new Windows library, or switch to an alternate method of doing the same thing (ie Invoke Code instead of the Microsoft ‘Remove from Dictionary’ activity).

3

(we also remember your skill set and do know, that we dont have to tell you things like WFA as you already know it)

there are several techniques, as not all is available to get handled by tools:

  • we can collect and identify activities by its name / schemas
  • e.g. prefix:name from the xaml
    where we map the prefix namespace to the referenced package/assembly

So we can setup some custom XAML - XML Processings Or Mass Text Processings and filling up this tool gap

A more Studio integrated approach is to remove the package in Legacy and get hints by the unresolved packages.

Example: Microsoft.Activities package v 1.0.1

  • it has many activities
  • we assume that only a fraction is used
  • a lot of replacements / alternate handlings can be found

So the strategy could be by forced breaking package wise to do the portings directly in Legacy before converting. Mapping Set PRE-Working

Benefit: we can also refer to the older implementation details. Once everything is done, we can go ahead to next

Migration Landing page:

1 Like
4

Thank you @ppr for your reply!!

Well I am glad to be reminded about my skillset :stuck_out_tongue:

Even though I knew 1 or 2 things that can be done, your detailed explanation is really making me think of various alternatives to solve this problem.

I was feeling stuck between different options, but now I have a better idea on how others are also approaching this scenario, you know what I mean knowing all those different ways to solve a problem, it really helps in picking out the better way to solve a problem.

Thank you so much for sharing this!!
And more thanks for making me think more :slight_smile:

Regards
Sonali

5

Thank you for your inputs.

Regards
Sonali

6

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.