By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,581 Members | 2,023 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,581 IT Pros & Developers. It's quick & easy.

Sharing logic between .Net Framework 4.6.2 and .Net Core 2.2

P: 1
I work with a legacy application written in .Net Framework 4.6.2 and I finally have the chance to start rewriting part of it in .Net Core. Current (legacy) code makes writing unit tests harder than it should among other problems.

During the (possible) migration, both legacy and new versions would have to be kept running since not all functionality can be rewritten at once. So, I was thinking if anyone would suggest ways to make this happen.

The obvious way that comes to my mind is to create a .Net Standard project and migrate the code there. I do know from research that this would be happen if the legacy application were targeting .Net 4.7.2 if I'm not mistaken. Maybe I can do that.

But going the .Net Standard way would mean impacting the legacy application. And also, I'm pretty sure there's a lot of logic in that project that can't be placed in a .Net Standard project.

So, are there any other ways?

1 Week Ago #1
Share this question for a faster answer!
Share on Google+

Post your reply

Sign in to post your reply or Sign up for a free account.