Re-branding is challenging and tricky. It may only seem that slightly enhancing the logotype can't do harm, in fact even tiny corrections can push customers away. We are people of habit and changes scare us. Considering this, not every company is brave enough to risk its time-proven widely-known face. Take a look at some of...

I wrote a Tiny Virtual Operating System for a 300-level OS class in C# for college back in 2001 (?) and later moved it to VB.NET in 2002. This is all pre-.NET Core, and on early .NET 1.1 or 2.0 on Windows. I moved it to GitHub 5 years ago and ported it to .NET Core 2.0 at the time. At this point it was 15 years old, so it was cool to see this project running on Windows, Linux, in Docker, and on a Raspberry Pi...a machine that didn't exist when the project was originally written. NOTE: If the timeline is confusing, I had already been working in industry for years at this point but was still plugging away at my 4 year degree at night. It eventually took 11 years to complete my BS in Software Engineering. This evening, as the children slept, I wanted to see if I could run the .NET Upgrade Assistant on this now 20 year old app and get it running on .NET 6. Let's start:$ upgrade-assistant upgrade .TinyOS.sln-----------------------------------------------------------------------------------------------------------------Microsoft .NET Upgrade Assistant v0.3.256001+3c4e05c787f588e940fe73bfa78d7eedfe0190bdWe are interested in your feedback! Please use the following link to open a survey: https://aka.ms/DotNetUASurvey-----------------------------------------------------------------------------------------------------------------[22:58:01 INF] Loaded 5 extensions[22:58:02 INF] Using MSBuild from C:Program Filesdotnetsdk6.0.100[22:58:02 INF] Using Visual Studio install from C:Program FilesMicrosoft Visual Studio2022Preview [v17][22:58:06 INF] Initializing upgrade step Select an entrypoint[22:58:07 INF] Setting entrypoint to only project in solution: C:UsersscottTinyOSsrcTinyOSCoreTinyOSCore.csproj[22:58:07 INF] Recommending executable TFM net6.0 because the project builds to an executable[22:58:07 INF] Initializing upgrade step Select project to upgrade[22:58:07 INF] Recommending executable TFM net6.0 because the project builds to an executable[22:58:07 INF] Recommending executable TFM net6.0 because the project builds to an executable[22:58:07 INF] Initializing upgrade step Back up project See how the process is interactive at the command line, with color prompts and a series of dynamic multiple-choice questions? Interestingly, it builds on the first try, no errors. When I manually look at the .csproj I can see some weird version numbers, likely from some not-quite-baked version of .NET Core 2 I used many years ago. My spidey sense says this is wrong, and I'm assuming the upgrade assistant didn't understand it. <!-- <PackageReference Include="ILLink.Tasks" Version="0.1.4-preview-906439" /> --> <PackageReference Include="Microsoft.Extensions.Configuration" Version="2.0.0-preview2-final" /> <PackageReference Include="Microsoft.Extensions.Configuration.Json" Version="2.0.0-preview2-final" /> <PackageReference Include="Microsoft.Extensions.DependencyInjection" Version="2.0.0-preview2-final" /> <PackageReference Include="Microsoft.Extensions.Options.ConfigurationExtensions" Version="2.0.0-preview2-final" /> I also note a commented-out reference to ILLink.Tasks which was a preview feature in Mono's Linker to reduce the final size of apps and tree-trim them. Some of that functionality is built into .NET 6 now so I'll use that during the build and packaging process later. The reference is not needed today. I'm gonna blindly upgrade them to .NET 6 and see what happens. I could do this by just changing the numbers and seeing if it restores and builds, but I can also try dotnet outdated which remains a lovely tool in the upgrader's toolkit. This "outdated" tool is nice as it talks to NuGet and confirms that there are newer versions of certain packages. In my tests - which were just batch files at this early time - I was calling my dotnet app like this:dotnet netcoreapp2.0/TinyOSCore.dll 512 scott13.txt This will change to the modern form with just TinyOSCore.exe 512 scott13.txt with an exe and args and no ceremony. Publishing and trimming my TinyOS turns into just a 15 meg EXE. Nice considering that the .NET I need is in there with no separate install. I could turn this little synthetic OS into a microservice if I wanted to be totally extra.dotnet publish -r win-x64 --self-contained -p:PublishSingleFile=true -p:SuppressTrimAnalysisWarnings=true If I add -p:EnableCompressionInSingleFile=true Then it's even smaller. No code changes. Run all my tests, looks good. My project from university from .NET 1.1 is now .NET 6.0, cross platform, self-contained in 11 megs in a single EXE. Sweet. Sponsor: At Rocket Mortgage(R) the work you do around here will be 100% impactful but won't take all your free time, giving you the perfect work-life balance. Or as we call it, tech/life balance! Learn more.(C) 2021 Scott Hanselman. All rights reserved.     

Latest PECL Releases:opencensus 0.2.0- Adds Span kind (#151) Adds Span sameProcessAsParentSpan (#153) igbinary 2.0.6RC1* Fix a bug in Windows debug builds. * Emit more specific warnings when __sleep() returns a declared property that was unset. * Fix harmless compiler warnings during builds. * Fix a build error on PHP7.3-dev. xdebug 2.7.0alpha1Sun, Apr 1, 2018 - xdebug 2.7.0alpha1 = Improvements: Fixed issue #938: Support remote debugging for PHP scripts that fork. (Sponsored by Brad Wilson) Fixed issue #1487: Re-enable IPv6 test on Travis. = Fixed bugs: Fixed issue #1526: Namespace filter does equality match instead of prefix match. Fixed issue #1532: SIGABRT when using remote debugging and an error is thrown in eval(). Fixed issue #1543: Various memory leaks due to changes in (internal) string handling. jsonnet 1.3.0- Update Lib JsonNet use v0.10.0. - Support PHP 7. cmark 1.0.0- initial pecl release gRPC 1.10.1RC1- gRPC C Core bug fixes #14747, #14787 swoole 1.10.3- Added swoole_event_dispatch - Added swoole_event_isset - Optimized accept performance - Added before parameter to swoole_event_cycle - Added swoole_process::setBlocking - Added swoole_http_request::getData

The Laravel News site has a quick tutorial posted showing you how you can use Eloquent functionality to help prepare your URLs and make them easier to maintain across the application. The key is in the use of "presenters". It's not uncommon to have tens, if not hundreds of views in a Laravel application. Something that soon gets out of hand is the various references to routes. [...] If for whatever reason we have to make a change to either the route alias or default query string values you'll soon find yourself doing mass string replacements across your entire application which brings the risk of breakage within many files. What can we do to possibly better handle this? There are a couple of different approaches. They provide two approaches, one being slightly more complex (but flexible) than the other. The first makes use of only Eloquent to define a getUrlAttributes method in the model. The second method abstracts this functionality out to a "URL Presenter", a class that defines methods for each of the CRUD actions and returns the correct route for each. The getUrlAttribute then returns an instance of this instead, making it easy to reference the method and route required in the Blade template.

Inspirational websites from the past couple of weeks that shine with a brilliant design. The post Inspirational Websites Roundup #39 appeared first on Codrops.

Affinity is an exciting program for any artist or designer looking for a Photoshop alternative. See our list of the top best Affinity brushes & get started!

This week's Designer News - No 580 - includes The Never-Ending Job of Selling Design Systems, Getting The Most Out Of Git, Simple CSS Line Hover Animations for Links, Pixel Bootstrap 5 UI Kit, An Interactive Guide to CSS Transitions, Lots of Free Icon Sets and so much more! The post Weekly News for Designers No 580 appeared first on Speckyboy Design Magazine.

Every day, the ProgrammableWeb team is busy, updating its three primary directories for APIs, clients (language-specific libraries or SDKs for consuming or providing APIs), and source code samples.

When it comes to creating and maintaining a website, the first thing that comes to any person's mind is a site's design. Well, design matters indeed, moreover, it can even influence your website's traffic, which in turn has an impact on the amount of money you make. In fact, a decent layout makes any website...

In this episode, we ask if Sass is still relevant in 2022 and if it adds any value modern CSS workflows. Vitaly talks to expert Stephanie Eckles to find out.