jmalarcon/dotnetversions

Command line tool that shows the currently installed "classic" .NET versions in your system

Howdy! 👋

⚡ I'm Jose Alarcón, from rainy Galicia, in the northwest of Spain (Europe). I'm an engineer, entrepeneur, writer and speaker.

💻 My code is mainly focused in 🌐 Web develoment: Front-End with JavaScript, and backend with C# and the .NET Framework, although I do a lot of this and that with other langs, frameworks and tools.

💬 Ask me about anything related to online training in Spain, which is what I do for a living.

📫 You can reach me through:

• My developer's YouTube Channel
• My personal YouTube channel, about software
• My blog about software
• My company's tech blog
• My personal non-tech blog
• Twitter
• Instagram
• TikTok

These are my highlighted Open Source projects at GitHub:

dotnetversions's Issues

.NET Framework compatibility

According to your documentation, DotNetVersions should require .NET Framework 2.0 to be executed. Even though I have the latest .NET Framework 4.8 installed (the Developer Pack edition), when I execute DotNetVersions, it triggers the missing runtime dialog:

Is it expected? I thought that .NET Framework should be backwards compatible. Do I really need to install .NET Framework 3.5?

Doesnt automatically exit.

Tested this on bare metal install of windows and also clean install of windows in a VM, in both cases it detects all .NET versions up to 4.8 then sits there until I abort, the longest case just over 6 hours, whilst sitting there I see no i/o or cpu activity from the process.

Seems hitting enter causes it to exit as well, so is it finishing but just not auto exiting? The bare metal also has newer versions of .NET which dont show, hence me waiting.

Seems by design this is only for older versions of .NET so i guess its just about the exit behaviour.

#3 (comment)

Support for .net core runtime version

Is there a way to include a check for .net core runtime version.

Version display

Hello, I know this nice little app for a long time, but it always reminds me to ask this question:
Shouldn't is say "4.8.1" somewhere? Not sure everyone will know 4.8.09037 is 4.8.1...

How to run the tool ? Updating of the Readme file

I was looking for an .exe file so I can run it and get the version of .net.

An update to the README.md can help with this so I know what I am supposed to do to get the version of the .net running on my system.

Is it supposed to be that I have to download and run the project locally to get the correct version ?

Providing an .exe file / more details on how to run the project

Via the microsoft docs I found your project. It looks promising but I wasn't able to run the project. For me it would be helpful to have a directly executable file or a brief instruction on how I could get the project to run 🤓

Missing one thing

Runs great! Just would really like to request feature that adds file path to each version...thanks!

VirusTotal has 3 vendors flagging this as malicious

FYI

https://www.virustotal.com/gui/file/647bf21ffaa77136799acf979056df96968e9959bb4e03c1622a20cfbc3802a1

Might be worth contact them and submitting for re-evaluation?

Make into a `dotnet` tool?

The dotnet CLI has a handy feature of "tools" (like extensions). I could see this being a very useful one. It would make your tool very easy to install & use.

https://docs.microsoft.com/en-us/dotnet/core/tools/global-tools
https://docs.microsoft.com/en-us/dotnet/core/tools/global-tools-how-to-create

Support running on .NET Framework 4 and later

This tool targets .NET 2.0, which means by default it will only run if you have a 2.0 to 3.5 runtime installed. On all currently supported versions of Windows, the 3.5 runtime is an optional component that is not installed by default. Windows will prompt you to download 3.5 if you try to run this tool and only have 4+ is installed.

One option is to create an app.config file to enable forward compatibility. To prefer 4+ but still run back to 2.0, you want something like this:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <startup> 
        <supportedRuntime version="v4.0"/>
        <supportedRuntime version="v2.0.50727"/>
    </startup>
</configuration>

Unfortunately, you no longer have a single file deployment, but I think that's the only option other than retargeting.