.
I composed a Tiny Virtual Os for a 300-level OS class in C# for college back in 2001 (?) and later on moved it to VB.NET in 2002 This is all pre-. Internet Core, and on early.NET 1.1 or 2.0 on Windows. I moved it to GitHub 5 years back and ported it to.NET Core 2.0 at the time At this moment it was 15 years of ages, so it was cool to see this task operating on Windows, Linux, in Docker, and on a Raspberry Pi … a maker that didn’t exist when the task was initially composed.
KEEP IN MIND: If the timeline is puzzling, I had actually currently been operating in market for many years at this moment however was still addressing my 4 year degree during the night. It ultimately took 11 years to finish my BS in Software Application Engineering.
This night, as the kids slept, I wished to see if I might run the Internet Upgrade Assistant on this now twenty years old app and get it running on.NET 6.
Let’s start:
$ upgrade-assistant upgrade.TinyOS.sln
-----------------------------------------------------------------------------------------------------------------
Microsoft.NET Upgrade Assistant v0.3.256001 +3 c4e05c787f588e940fe73bfa78d7eedfe0190bdWe have an interest in your feedback! Please utilize the following link to open a study: https://aka.ms/DotNetUASurvey
-----------------------------------------------------------------------------------------------------------------[22:58:01 INF] Filled 5 extensions
[22:58:02 INF] Utilizing MSBuild from C: Program Filesdotnetsdk6.0.100
[22:58:02 INF] Utilizing Visual Studio set up from C: Program FilesMicrosoft Visual Studio2022Preview [v17]
[22:58:06 INF] Initializing upgrade action Select an entrypoint
[22:58:07 INF] Setting entrypoint to just predict in service: C: UsersscottTinyOSsrcTinyOSCoreTinyOSCore.csproj
[22:58:07 INF] Advising executable TFM net6.0 due to the fact that the task develops to an executable
[22:58:07 INF] Initializing upgrade action Select task to update
[22:58:07 INF] Advising executable TFM net6.0 due to the fact that the task develops to an executable
[22:58:07 INF] Advising executable TFM net6.0 due to the fact that the task develops to an executable
[22:58:07 INF] Initializing upgrade action Back up task
See how the procedure is interactive at the command line, with color triggers and a series of vibrant multiple-choice concerns?
Remarkably, it develops on the very first shot, no mistakes.
When I by hand take a look at the.csproj I can see some unusual variation numbers, likely from some not-quite-baked variation of.NET Core 2 I utilized several years back. My spidey sense states this is incorrect, and I’m presuming the upgrade assistant didn’t comprehend it.
<