.NET Core 7 or .NET Core 7
120 views
Skip to first unread message
José Penalva
Feb 6, 2023, 2:01:57 AM2/6/23
to Migrated By Firefly
Any news about .Net Core 6 or 7 support by FireFly ?
Noam Honig
Feb 6, 2023, 2:55:05 AM2/6/23
to José Penalva, Migrated By Firefly
We’re still waiting for Microsoft to release the visual studio windows forms designer for .net core. It is currently only in preview stage and supports only the basic use cases.
We are waiting for Microsoft to complete that because we believe that being able to design windows forms is critical for desktop applications
On Mon, Feb 6, 2023 at 09:02 José Penalva <jpena...@gmail.com> wrote:
Any news about .Net Core 6 or 7 support by FireFly ?
--
You received this message because you are subscribed to the Google Groups "Migrated By Firefly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to migrated-by-fir...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/migrated-by-firefly/86852708-890b-4535-9867-5a16f6fe52fbn%40googlegroups.com.
Maciej Kokociński
Sep 29, 2023, 2:17:07 AM9/29/23
to Migrated By Firefly
Hi Noam, do you see a chance to compile Firefly.Box.dll in .net 7. I am asking this because we are thinking about converting our application to .net 7 and we need your support in this matter.
Noam Honig
Sep 29, 2023, 4:40:36 AM9/29/23
to Maciej Kokociński, Migrated By Firefly
Hi Maciej,
The migrated code and the ENV and Friefly source code are highly compatible with .NET core > 98% according to analysis tools.
Because Microsoft Visual Studio has not yet completed its work on a Visual Form Designer for .NET core - we did not complete the adjustment to .NET Core, since we don't believe anyone will buy a migration to .NET without a Visual Form Designer.
Because Microsoft Visual Studio has not yet completed its work on a Visual Form Designer for .NET core - we did not complete the adjustment to .NET Core, since we don't believe anyone will buy a migration to .NET without a Visual Form Designer.
Since you have all the source code, you can perform the move to .NET Core yourself - one of our customers did that a few months ago and although it required some work, they seem to be happy about it - Maybe they can respond to this forum post.
As for the Visual Designer, the best advice I have at this point is to use two project files, for the same C# files.
One with .NET Framework - to use with the visual designer, and one with .NET Core to compile and use .NET Core 7.
Since we haven't done a .NET Core migration ourselves I don't have a lot more information to give you - other than that one of our customers has done it and as far as I know succeeded.
I recommend that you either postpone until we've done it or try to do it with the source code you have - contracting us to help is also an option, but it'll be with a significant cost
Best
To view this discussion on the web visit https://groups.google.com/d/msgid/migrated-by-firefly/ea31e9d4-e9e5-4e90-84c9-04247d054ec0n%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages