VisualRecode

The Hassle-Free Code Upgrade Tool for .NET
Easily migrate WCF applications to gRPC

[VisualRecode @VisualRecode]

Looking to migrate a WCF application to .NET 6?

Well, you can with Visual ReCode 2022.1! This release adds .NET 6 as a target framework for WCF to gRPC migrations.

You can read more about our newest update on the blog:

https://t.co/CiKae7zbE7

[VisualRecode @VisualRecode]

@SimonHolman Not yet. It's still in the hopper, but we've found the well of "interesting" WCF configurations customers have was deeper than we ever imagined.

[VisualRecode @VisualRecode]

Great article from the @azuread team on how they halved their Azure Compute requirements (and therefore costs!) by migrating the gateway from #dotnet 4.6.2 to #aspnetcore 3.1.
https://t.co/uSM2tisSFI

[Alexandre Mutel @xoofx]

During the work on Blake3 for .NET, first time that I have started to play with some new .NET 5 features like `SupressGCTransition`: this little attribute is great to squash the last bits of performance for interop scenario...

https://t.co/y5f2MHkT9p

[VisualRecode @VisualRecode]

Planning to have a 2.0 release supporting .NET 5.0, and with some major new features, around this time.
https://t.co/UemoTjmQEA

[Dave McCollough @davemccollough]

Mark your calendars! .NET Conf 2020 #dotnetconf https://t.co/8jZpFe4tf9

[James Newton-King ♔ @JamesNK]

New gRPC documentation: Create Protobuf messages for .NET apps

This doc summarizes content from the "gRPC for WCF developers" by @markrendle

https://t.co/dARyNDdK0i

[VisualRecode @VisualRecode]

Upgrade your .NET Framework Applications to .NET Core without rewriting.
Try Visual ReCode for FREE!

[VisualRecode @VisualRecode]

New release with the first beta of .NET 4 to .NET Core project migration, supporting WPF, WinForms and more!
https://t.co/Mdz02l8E9N

[VisualRecode @VisualRecode]

Have you watched all the .NET content from #MSBuild already? Need some more? We've got you covered. Watch @markrendle 's talk ".NET Is Dead. Long Live .NET" from @dotnet_fwdays
now: https://t.co/B6RdzSPfht

[VisualRecode @VisualRecode]

@ladeak87 @markrendle That's always been the plan, and we're getting closer and closer!

[Rendle Has Left The Dumpster Fire @markrendle]

The @VisualRecode Project Migrator even checks your NuGet packages are Core-compatible, and upgrades them if a later version is (e.g. upgrading Entity Framework to 6.4).

[Rendle Has Left The Dumpster Fire @markrendle]

Watching #MSBuild and pondering updating your code to the new #dotnet?
Here's a sample migration report from @VisualRecode showing issues when migrating a WinForms app from .NET 4.6.1 to #dotnetcore 3.1:

[VisualRecode @VisualRecode]

@MicbOliver *muwahahaha!*

Yup.

[VisualRecode @VisualRecode]

Looking forward to the #dotnet 5 content at #MSBuild! Nearly ready to launch our next beta feature: Net4.x -> NetCore3.1 project conversion for WPF, WinForms and more.

[VisualRecode @VisualRecode]

In 20 minutes our @markrendle will be live streaming on #DevAroundTheSun, talking about the Evolution of Computing. Watch at https://t.co/KXEZNfATYe or https://t.co/11pm1OfsOS and please donate!

[VisualRecode @VisualRecode]

Visual ReCode 1.1 is out! A few bug fixes, and a new feature to generate a #WCF proxy to your new #gRPC application to support service consumers who can't update their apps to consume gRPC right away.

More info: https://t.co/RkYD2e8qGp

[VisualRecode @VisualRecode]

You could be running your #WCF services in @GCPcloud #CloudRun if you upgrade them to gRPC. We can help with that!
https://t.co/r4RzSHju6x

[VisualRecode @VisualRecode]

Visual ReCode 1.0 is now available! Find out more at https://t.co/Hd13zAwpjh and download a free 14-day trial copy today!

[VisualRecode @VisualRecode]

@bjartnes Interesting, thanks!

[VisualRecode @VisualRecode]

Dear #aspnetcore developers,

Which Swagger package do you prefer for adding OpenAPI to your web API projects? And if you've got a minute, please let us know why in the replies.

Thank you!

[VisualRecode @VisualRecode]

@darrel_miller @markrendle Oh, I wasn't aware they'd trademarked it. Thank you for clarifying :)