Microsoft .net Framework 3.5 Needs To Be Installed

[Mica Withington]

ArcGISPro 3 requires .Net Framework 6.0 (64 bit) but there are MANY versions available. ESRI also specifies that a Windows Installer must be used (why?). It appears the installer that most would use, Microsoft Windows Desktop Runtime 6.0.x is not enough to get ArcGIS Pro to work. One actually needs Download ASP.NET Core 6.0 Runtime (v6.0.16) - Windows x64 Installer (microsoft.com) as well.

Hi @RichardDaniels Thanks for submitting this idea to improve the documentation. The requirements do state that ".NET Desktop Runtime 6.0.5 or a later patch release" is required: -app/latest/get-started/arcgis-pro-system-requirements.htm

The 6.0.5 link goes here: -us/download/dotnet/thank-you/runtime-desktop-6.0.5-windows-x64-installer. Clicking on that will directly download the correct minimum required version to run ArcGIS Pro 3.x. The 'a later patch release' does point to the overall download page, as I believe you're alluding to, because there will continue to be patch releases to that version of .NET that we can't link to from the doc before they exist.

When you say Windows Desktop Runtime..." do you mean ".NET Desktop Runtime..." which is what is indicated in the documentation? And links here: -us/download/dotnet/6.0 It looks like when that is downloaded and installed on the machine, it displays as Microsoft Windows Desktop Runtime - 6.0.16 (x64), so we're probably talking about the same thing.

I have a machine with ArcGIS Pro 3.1.1 and previously had 6.0.14 on it. You can see from the screenshot above that I just installed 6.0.16 and Pro opens and works fine. So unfortunately if that is not working for you, I don't think that it is a problem that a documentation update will fix.

I understand the desire for the documentation to tell the user exactly what is needed, but as noted above, there are multiple and sometimes frequent patch updates issued by Microsoft. Also the system requirements are just that, the minimum requirement to run the software in a supported manner. That minimum (.NET Desktop Runtime 6.0.5) is linked to explicitly and downloaded automatically without the user needing to make a decision or research the latest .NET 6.0.x patch available.

We're discussing this with the documentation team to see if there is an opportunity to improve how this is described and delivered in the system requirements topic. For the issue of Pro not working with certain versions of .NET as you've indicated above, we can't address that through documentation. Please troubleshoot with technical support.

During installation of ArcGIS Pro 3.3, if we detect that .NET 8 is not present on the machine we will provide a message - in that message we are including a hyperlink to the .NET 8 download page as a response to this feedback. We hope that helps in situations like this one.

Thank you for updated the documentation. I would say that our issue was not a 'one-off', we have over 1800 machines in our environment with ArcGIS Pro and ArcGIS Desktop and it took several days to track down the correct version of .Net 6 to install.

Dear Lifehacker,

What is the "Microsoft .NET Framework" and why do I need it? I've been trying to install BlackBerry Desktop, but it fails and states I'm missing the Framework. For some reason I can't download it from Microsoft. What could I do?

Dear Needing,

.NET is a programming framework created by Microsoft that developers can use to create applications more easily. As commenter dwroth aptly put it, "a framework is just a bunch of code that the programmer can call without having to write it explicitly."

In a perfect world, you wouldn't need .NET Framework. The makers of all your crucial applications would have the time and resources to fully patch together their applications into self-contained packages, because developing for Windows would be an intuitive, mostly high-level process that independent developers could nail down in fairly quick order. So nobody besides developers would need a package like .NET, which provides applications with an orderly way to access databases, web services, and other communication tools.

Most times, applications will ask for a particular version of the framework to be installed. We'd recommend avoiding installing that particular version, and trying instead to install the most up-to-date version of .NET, assuming your Windows OS supports it. Most .NET packages have backwards compatibility, so an app asking for the 2.0 framework can usually get by with what's packaged into the latest version: .NET Framework 4. Be sure, too, that you're settled up on your Windows Update requests, as there may be relevant system patches that need installing before .NET will fit comfortably on your system.

One problem .NET installations often run into is a need for space, even if your system might not make that explicit. The 4.0 version of .NET for standard 32-bit Windows systems requires 850 MB of free space on your primary Windows drive; a 64-bit Windows system needs 2 GB free, and Windows usually won't ask you if you have space on another partition to spare. If your free space is smaller than these amounts, you'll need to look at your hard drive and free up some space.

Another common problem involves older versions of .NET and, perhaps, their misbehavior on your system. Head into your Add/Remove Programs section in Control Panel (or "Uninstall Programs" in newer Windows setups) and search for any installations related to ".NET Framework," or something very similar. Try removing them from here, through the standard uninstall procedure, then try installing your newer .NET framework again. If that still fails, it's time to turn to the .NET Framework Cleanup Tool, which was made by Microsoft itself to tidy up and set things straight following tricky .NET installations.

On a fresh install of Windows 8.1, first thing I did (as I usually do) is install Intel Graphic driver but the driver, greeted me with a message that .Net framework is needed to install the driver although the system is fully updated with .Net framework 4.5, 4.6.1, 4.7.2, 4.8 & 3.5 installed. I checked twice.

The first software to be installed after Windows installation and before installing any other drivers, is the Intel Chipset Device Software. This action ensures that Windows recognizes all chipset components. You may download the Intel Chipset Device Software from the OEM site.

Thank you for the response. I have installed the chipset driver but still couldn't run the graphic driver installer, complains .Net framework is missing. Not doing anything else on the machine unless this is fixed.

The .exe packages needs fixing. They shouldn't have any dependencies like VB runtime and/or frameworks. Users usually install drivers before installing anything else and/or going online. A self extracting archive with a script to initiate the igxpin.exe with arguments should suffice and save lots of hassle.

Could you please forward my request the development team, if possible ? My next machine is going to be Intel too and I don't want to deal with the .zip files when it comes to the driver installers. I prefer. exe packages.

But it didn't happen with the driver of this model, it happened with all of the .exe's I downloaded. After speculating that issue is with the .exe archive, I downloaded other random .exe packages to check if they get unpacked or not and they returned the same error.

However, due to this product being discontinued, Intel Customer Service no longer supports inquiries or feedback for it. You may also find the Discontinued Products website, helping to address your problem.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

One of the things you can do to check the .NET Framework versions on your machine is to run an elevated command prompt with the command reg query "HKLM\SOFTWARE\Microsoft\Net Framework Setup\NDP" /s. This will report all installed versions, and there might be a considerable number (don't delete any). Search the list for the latest and make sure it meets the criteria of Garmin Express. A search seems to indicate that .NET Framework 4.7.2 is needed. Microsoft also has a .NET Repair Tool that might be worth running. It can be found at www.microsoft.com/.../details.aspx

Even though .NET is installed, is it enabled to run? The attached graphic shows what is enabled om my Win 10 machine. Note that if you make changes, you likely have to reboot for them to take effect.

I can't speak as to why .NET Framework 3.5 may be needed by Garmin Express and I'm not about to uninstall it from my PC to do a test. My Win 10 machine is running the exact version you are running and from all appearances .NET 3.5 is needed by something. Microsoft does not recommend uninstalling old versions of .NET, but having said that there is evidence that if you do and a specific app needs a specific .NET version, the user will be prompted. So apparently since you are being prompted, some need perhaps does exist. If you go to the area that turns Windows features ON/OFF is 3.5 (assuming it exists) enabled?

The binaries interact with each other and must be kept in the same folder for the assembly to work. In rare situations this is not possible (e.g. when installing the assembly to GAC), make use of the Session.ExecutablePath property to force the assembly to look for the winscp.exe in a different location.

E.g. If you reference WinSCP assembly from your project in Microsoft Visual Studio, it copies the assembly during build into the project Output path (e.g. /obj/Debug). Similar case is when you install the assembly into Global Assembly Cache (GAC).

You may want to add winscp.exe to your Visual Studio project, to have it copied to the Output path automatically (by setting file property Copy to Output Directory to Copy if newer). The Build Action should be automatically set to Content, what means that the file will be included when deploying your application (e.g. an ASP.NET web application, Azure WebJob or Azure Function).

3a8082e126