GetFiles and EnumerationOptions

Anonymous

Question at top to avoid long scrolling below.

I have tried so many thing, downloading/installing many 'versions' (5,6,7,8,9) and have not had a single sucess in my trials trying to use (as below). In almost every case I only ever get 'not found' errors.

What do I need to install to make use of this?

public System.IO.FileInfo[] GetFiles (string searchPattern, System.IO.EnumerationOptions enumerationOptions);

from:

https://learn.microsoft.com/en-us/dotnet/api/system.io.directoryinfo.getfiles?view=net-8.0#system-io-directoryinfo-getfiles(system-string-system-io-enumerationoptions)

which applies to:

.NET Core 1.0, Core 1.1, Core 2.0, Core 2.1, Core 2.2, Core 3.0, Core 3.1, 5, 6, 7, 8, 9

My current version:

Microsoft Visual Studio Community 2022

Version 17.10.0 Preview 4.0

VisualStudio.17.Preview/17.10.0-pre.4.0+34814.14

Microsoft .NET Framework

Version 4.8.09032

Installed Version: Community

ASP.NET and Web Tools 17.10.319.52870

ASP.NET and Web Tools

Azure App Service Tools v3.0.0 17.10.319.52870

Azure App Service Tools v3.0.0

C# Tools 4.10.0-3.24211.4+e482b6e281d7db727fcb086ebbfae44dcba82c6d

C# components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.

GitHub Copilot 0.2.860.47384

GitHub Copilot is an AI pair programmer that helps you write code faster and with less work.

Microsoft JVM Debugger 1.0

Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines

NuGet Package Manager 6.10.0

NuGet Package Manager in Visual Studio. For more information about NuGet, visit https://docs.nuget.org/

TypeScript Tools 17.0.30327.2001

TypeScript Tools for Microsoft Visual Studio

Visual Basic Tools 4.10.0-3.24211.4+e482b6e281d7db727fcb086ebbfae44dcba82c6d

Visual Basic components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.

Visual F# Tools 17.10.0-beta.24172.5+8d852e43d35fdac96b1ba52e3bd4b35350035914

Microsoft Visual F# Tools

Visual Studio IntelliCode 2.2

AI-assisted development for Visual Studio.

Anonymous

2024-04-26T14:58:34.06+00:00

Just a jog to try and get this forum to catch up. I see there is a reply/answer timed at 3:12 - about 45 min ago. Maybe the forum will eventually take it's

head out of the sand and reveal to me what has been posted!

YEAH! the reply has appeared thanks to this junk post.
Jiale Xue - MSFT 33,686 Reputation points Microsoft Vendor

2024-04-29T12:58:24.87+00:00

What's up to date with the latest developments?Do you have the .net Framework modules installed correctly?Have you tried to create a .NET Framework 4.8 console project to test?
Les 0 Reputation points

2024-04-29T15:37:36.4566667+00:00

Hi

I suppose you are asking me. I have made some progress, and for the moment I am trying various test scenarios to check some of the functions. I am both new to C# and to the 'Code' versions (using NET 9 Preview at the moment) My 'breakthrough' was when I discovered that I could simply choose a Template to facilitate a 'SDK style' Project. That simple thing overcame a long series of searching and questions etc, Although I can not yet be 100% sure, I am able to create and test code using the EnumerationOptions() that tempted me to pursue this escapade into 'Code' versions.
Les 0 Reputation points

2024-04-29T16:19:14.2+00:00

See last post in this thread

2 answers

Michael Taylor 48,581 Reputation points

2024-04-26T14:12:27.26+00:00
Please be more specific about your error. When do you get "not found"? Is this a compiler error or when you run your code? Since it seems code related then please post the code that isn't working.

The method in question has been around a long time and the following simplistic example shows how to use it.

var dir = new DirectoryInfo(@"C:\temp"); var files = dir.GetFiles("*.txt", new EnumerationOptions() { MaxRecursionDepth = 2 }); foreach (var file in files) { Console.WriteLine(file); };

Note that if you're using .NET Standard 2.0 then you also need a using System.IO in your file.
Please sign in to rate this answer.
Anonymous

2024-04-26T15:42:12.4766667+00:00

Hi

Thanks for your reply.

Error on "EnumerationOptions" keyword at time of entry:

Error (active) CS0246 The type or namespace name 'EnumerationOptions' could not be found (are you missing a using directive or an assembly reference?) but I have no idea what I need to reference.

FTI: I used your code to generate that error in a fresh Project.

Michael Taylor 48,581 Reputation points

2024-04-26T16:04:28.1566667+00:00

What is the target framework for your project? Note that it was added to NET Standard 2.1 so if you are using NET Framework then it won't work as it wasn't defined for NF. You have to be targeting NET Core 3.1 or NET 5+.

Also note that this overload is for advanced scenarios. In general you can use the simpler overloads that use SearchOptions or no options and accomplish the same goal.

Anonymous

2024-04-26T16:30:39.7666667+00:00

Hi

Sorry, I am not able to follow any of that. I am not a guru and although long time VB user, I am not in any ay knowledgeable about all the variations and flavours available all of which have their own requirements. All I have been trying to do is download a version that provides that particular GetFiles method(s) which I am in need of.

As Mentioned, I have tried so many variations, all of which downloaded and installed but none of them allowed the Enumerations keyword at time of entry.

When you ask about BET Framework, then in the Properties of anu/all projects, I only get a set of NET Frameworks to choose from. (that was where I had originally thought I would get some indication of Core xx.xx as an option. Sadly, I was wrong.

Is there any download available that would install as do the others but make Code xx.xx available? I would willingly uninstall everything to get a fresh install (which I already tried during earlier attempts.

EDIT: I missed your edit. I do already have and use the 'standard' GetFiles as per your comment, but I wanted to use the 'newer' version - which has led me to this series of rabbit holes I find myself buried in.

Michael Taylor 48,581 Reputation points

2024-04-26T16:48:01.1833333+00:00

If you are using Net Framework then that overload is not available. Use one of the simpler overloads accepting either just the file pattern or the file pattern and search options.

If you must use the version that uses EnumerationOptions then you have to upgrade your project(s) to NET 6+. How easy or hard that is depends on your project types. It is not just a matter of changing the version information. They are completely separate runtimes. Let's run through some project types and what you need to do.

First, a note. NET Framework projects are generally still in the old project format. In order to use NET 6+ you have to use the newer SDK format. You can easily do this by hand if you know what you're doing but the easier approach is to use the Upgrade Assistant (UA) extension in Visual Studio to do it for you. However that requires you pick a newer framework so continue reading on what to do for each project. You must be using the SDK format to target (or multi-target) NET 6+. Furthermore all projects must have a common framework otherwise they cannot call each other.

If you have a class library that needs to support both NET Framework applications AND the newer NET 6+ projects then you have to multi-target your project. For the version that is used by NF apps you have to conditionally include calls to the overload as they aren't available in the older framework. If you only need to support NET 6+ projects then your class library can just target NET 6+. If you are using the UA then it can handle all the details except multi-targeting which you can manually add afterwards.

If you have a console application AND you are OK requiring NET 6+ runtime then you can run the UA to upgrade it. Unfortunately it won't migrate your configs and depending upon your third-party dependencies you will have manual work to do.

Web projects are the hardest. The UA extension will not do an inplace upgrade of an existing NET Framework app. Instead it'll create a new project and use YARP to proxy calls back to your old app. Unfortunately this is the only automated way to do that since web apps are too varied to migrate manually.
Sign in to comment
Bruce (SqlWork.com) 56,771 Reputation points

2024-04-26T16:50:37.41+00:00

to use that api, you need to create a .net 8 project. to run the sample in the link, create console app for windows, linux and macOs.

if you are using .NET framework (windows) only, then you are using the wrong docs. use:

https://learn.microsoft.com/en-us/dotnet/api/system.io.directoryinfo.getfiles?view=netframework-4.8
Please sign in to rate this answer.
Anonymous

2024-04-26T17:27:54.5533333+00:00

@Bruce (SqlWork.com) and @Michael Taylor Yes, I am currently using .NET framework and is working fine. It is when I decided to check out the 'newer' version that I ran out of understanding. Talking in abbreviations just means nothing to me. I had expected to be able to download a VS version and get on with it but sadly that didn't transpire. I mean, when it says "Applies to: x,y,z" and I download and install one (or all) and get nowhere it gets boring. It seems that no such thing exists so I will just make do with what I have. Thanks to both for your contribution(s).

Bruce (SqlWork.com) 56,771 Reputation points

2024-04-26T20:10:36.06+00:00

downloading a library or sdk does not magically add it to an existing project. you need to update the project.

also most api's have features by version (later versions have different feature or even breaking changes). if you are using 4.6 of an sdk and look at the docs for version 8, there is good chance of a mismatch. most api documentation states what versions that api call supports. if the version you project is using is not there, then probably its not supported.

the difference between .net framework (1.0-4.8) and .net 5+ is so great, that they have different documentation sets. (there was a .net core 1.0, 2.0, 3.1. but the release after 3.1 was named net 5.0 and dropped the core nomenclature).

if you are using .net framework, you should update your project to the latest supported version 4.8.1 and use the 4.8 documentation.

you could also depending on the project type update to .net 8. this is a more complex upgrade because there are a lot of breaking changes in api.

note: the .net framework is considered mature, and not being updated except for security fixes. it is also an optional workload install of visual studio. google is not your friend because nowadays, it generally will return the .net 5+ solution. look for answers dated years ago.

Les 0 Reputation points

2024-04-26T20:50:10.22+00:00

Hi

The version of VS I am using at the moment s from a download/install of NET 9. Even though, as I said, I only got the NET Framework targets listed. I had foolishly believed the various statements regarding 'Applies to' which said amongst others that the 'enumerations' would apply. Anyway, all this mix'n'mismatch is not for me.

I thank you for being so patient with my offbeat questions and lack of understanding. I will admit defeat and stick to NET Framework where a degree in Astrology is not needed.

Michael Taylor 48,581 Reputation points

2024-04-26T21:15:52.7433333+00:00

Visual Studio version doesn't impact the runtime version of your product. VS 2022 can support projects going back to NET Framework 4.x through the current NET 9 version. You still have to update your projects if you want to use the newer features. You upgrade if and when you're ready. Having separate copies of Visual Studio to support set versions of the runtime would be a tremendous waste of space.

To be honest this is how C++ works for Windows as well. Just because you install the latest version of the dev tool doesn't mean your app suddenly starts running on the latest Windows runtime. You still have to update your project settings to use the newer Windows libraries. This ensure installing a newer dev tool doesn't suddenly break your apps.

Unfortunately migrating from the Net Framework runtime to the NET Core runtime is a big deal and requires you to upgrade your project files. It is just the cost of the conversion. Once you are using NET Core projects then upgrading from NET 6 to NET 8/9/whatever is simply a matter of changing the target framework in the project settings. There are lots of articles online to help guide you through this upgrade process.

Les 0 Reputation points

2024-04-27T08:29:17.5566667+00:00

Hi

[Deleted]

Just deleted long comment regarding latest attempts.

Now, is this something! I decided to create a new C# project in my current version of VS. I started to do what I always do, and selected the suggested Template from 'Recent project templates', which of course was (the only one in the list), a Windows Forms App (NET Framework), when I noticed on the panel at the tight side, a Template called 'Windows Forms App' (no mention of Net FrameWork). Not knowing any better, I created one of those and was completely startled to find a choice of Framework - .NET 8.0 (long term support) or .NET 9.0 (Preview).

Selecting the latter I added your code from earlier in this thread and WOW, success. Compiled and ran fine (although I had to add a TextBox for output as Immediate and Output windows failed to show it.)

Now, I wonder if in fact, this is all I asked for ............... so far so good.

RLWA32 40,656 Reputation points

2024-04-27T10:56:32.8733333+00:00

@Les, I haven't used it but I think that the Upgrade Assistant is a Visual Studio Extension that you can install. Take a look at .NET Upgrade Assistant.

Les 0 Reputation points

2024-04-27T11:35:34.9433333+00:00

@RLWA32 Thanks, but see my amended post above tour one - I was composing it while yours arrived.

Les 0 Reputation points

2024-04-27T11:53:10.6866667+00:00

@RLWA32 downloaded and installed. Limited try out (failed to do anything much), found 2 issues on a test project but no offer to 'fix' or 'repair' or 'convert'? Don't really know what I was expecting but thanks anyway.

Michael Taylor 48,581 Reputation points

2024-04-27T14:42:28.0866667+00:00

Upgrade Assistant is an extension you install in Visual Studio. Once you restart VS then each supported project has an 'Upgrade' option in the context menu of the project in Solution Explorer. In general you upgrade projects from least dependencies to greatest. Note that once you start upgrading then you'll end up with a lot of compiler errors most likely for later projects as you're breaking the dependencies. Once the upgrades are done some of these errors go away so don't bother fixing errors in other projects until the upgrades are complete.

For class libraries the changes are minimal: switch to SDK project, change to target desired framework, fix up any Nuget package references to use compatible libraries, remove unneeded settings.

For apps the changes are more complex and generally won't include any migration from the *.config to the appsettings.json format. You have to migrate this yourself. Unfortunately apps are where all the changes get dificult because there are so many differences but that is the only way to upgrade automatically. If you want to create a new project and manually copy things over then you can do that as well but ultimately you'll be making the same changes. I only do this with web apps. For winforms apps either let the upgrade assistant do it (because there are property settings that must be set) or create a new project and copy over your stuff. Just be careful to copy all your app-specific project settings that you need + any resources.

Les 0 Reputation points

2024-04-27T18:07:33.4+00:00

Hi

Making some slow progress here. Have given up on the Upgrade function as it didn't seem to do much if anything - probably my ineptitude plays a part there. That is OK as since starting to use C#, past 10 days or so, I have only 4 projects, 3 small and 1 medium so it will not be a huge task to manually transfer them over, and try to make them work.

Thanks for the help.
Sign in to comment