whelaunch.blogg.se

1. Microsoft .net framework 4.6 for mac how to#
2. Microsoft .net framework 4.6 for mac upgrade#
3. Microsoft .net framework 4.6 for mac code#
4. Microsoft .net framework 4.6 for mac trial#
5. Microsoft .net framework 4.6 for mac windows#

Once you have stripped out everything leaving behind the UI, when the time comes you could look to replace the UI with a. net standard 2.0 libraries and move all the business logic, data access, etc (anything non-ui related and that isn't using 4.6 specific apis) to these libraries. net framework 4.8 (which I'd imagine should be painless, depending on what dependencies you have).

Microsoft .net framework 4.6 for mac code#

I'm going to assume you have mostly all your code in a single project targeting 4.6.

Microsoft .net framework 4.6 for mac windows#

I know you asked for examples, but things like being cross platform is of little benefit if all your customers are on windows (with exception of cheaper CI/CD). If it is simply "I want to be using the latest tech", that's not really an argument. NET 6 depending on who your customers are and what your motivations are. There may be little immediate benefit for you moving to. If you can find places to migrate parts at a time, that may help, especially if your product is modular, or split into libraries. Where I can't get Standard to work, I'm rewriting code into non shared Core libraries (for Core projects) with the plan of abandoning the Framework versions when the time comes. I've been moving library code to new Standard libraries (shared between Framework and Core) where I can, with the plan to convert those to Core when they aren't needed in Framework. I'm in a similar situation with a large Winforms, WPF, Windows Service, Library suite still in framework (about 40 projects in one solution), and while I really want to move forward to core, I also realize that rebuilding this all at once isn't realistic.Īnything new that can be written in Core has been for a couple of years now (and is being kept current with each Core release). How much of the code from the forms project is in libraries, or could be moved to libraries? Can you at least bring everything to Framework 4.8 (4.8 will have support for the long term)? NET Framework 4.6 to Core 6 is a process which doesn't affect end client, will take time and can provide tons of bugs and unnecessary amount of work.ĮDIT: as u/BCProgramming said, it will be harder and harder to find people willing to work in old technology, and people you're working with can always leave. Staying in older framework is also bad for workers, because instead of growing, learning new stuff and stuff which is actually used, they have to dabble in some old shit.īut if your app won't have any new features, and your only job is to maintain it, I doubt you will convince them. And probably nobody will fix packages bugs on older framework. NET Framework 4.6, so chances that the new feature which you will want to add will be created as a package decreases constantly. The longer you stay with old framework, the more challanging development process will be.Īlso no new packages are probably made for.

Microsoft .net framework 4.6 for mac how to#

If yes, as the time will pass it will be harded to add new features because it will be harder to find tutorials on how to operate on older framework and it will be harder to find people who could help you.

Microsoft .net framework 4.6 for mac upgrade#

I have little experience with Core 6 but I'll do what it takes to move forward.įirst question: do you plan to upgrade it, add new features?

Microsoft .net framework 4.6 for mac trial#

I know what I know from trial and error and spending the numerous hours it took to learn it. With that being said, I'm willing to put in the work to get it done. I want it to succeed and I'm willing to fight to make sure it does. I love this company and plan on staying here. I know the first thing that comes to mind is 'run away' but that's not an option. What is the best way to proceed? I'll be the first to admit, I'm probably over my head on this but I believe it has to be done, otherwise it'll become outdate and eventually not able to run on future operating systems. How do I sell him on this? This coming from a man who didn't see the benefits of putting an investment in to a website or social media. What are the benefits to moving to Core 6, that will help me persuade him? I believe it'd take two developers, which we do not have to place on this project, to move forward. I'm having a hard time selling him on the idea that we need to move to Core 6 instead of staying where we are at. The owner, who I've worked for 25 years, is in his upper years, like way up there. We have a huge application written in C# that has taken years to develop.