Why should you migrate your project?

legacy → windows :

  1. Is it because they will no longer support the .NET Framework (based on 4.6.1 or 4.8)?
  2. Is .NET 5/6 better?

Activity Classic → Modern
3. Is there a difference between classic and modern activities?
4. Will classic activities be discontinued?
5. Should we think that modern activities have better functionality than classic activities?

@sumouse,

Yes

It’s not about better or not, it’s about Support from Microsoft is no more for older versions.

Yes, there are differences.

No plans revealed from UiPath as of now.

It depends on activities.

Thanks,
Ashok :slight_smile:

  1. Yes
  2. Yes
  3. Yes
  4. Yes
  5. Yes

There is no good reason to not migrate.

1 Like

here it is also elaborated on arguments about migration

We should not mix up classic design / modern design with Legacy / Window Compatibility

However, lets address the questions as well:

Reference: Overview - Deprecation timeline

  • A formal date is currently not announced, but we can assume a phase out in the future

The word better should be bound on factors. So in short:

  • has advantages and disadvantages. But as we can expect the progress on the functionality we would focus Modern Design for UI-Interaction / Application related activities. For the latter mention we can also work within an Hybrid approach (e.g. Excel Classic and Excel Modern)