winforms | A collection of custom Controls for Windows.Forms | User Interface library

I think I got what you're trying to do. First of all, FTP doesn't itself let you use multiple connections simultaneously (For ref Uploading files in parallel with Java FTP client).

What you're doing is not thread-safe as well. So I advise you to make parallel connections and download from there.

Looks like you have resolved the embedding part of your question and are left with just the deletion of the extracted DLLs.

Because the DLL is inuse but your own process, unless you are able to uload the DLL successfully, I dont think you will be able to delete the DLL.

1st Potential Option

One thing you could try and do is schedule the deletion of the file after reboot. This SO post explains how to do that using P/Invoke and MoveFileEx.

The example they give is as follows:

You could modify the stored item value with $ListBox.Items.Item($CurrentIndex) = $Text.ToUpper() - but modifying a collection item in place is not going to trigger re-drawing the ListBox control, so it'll look like no change took place.

Instead, modify the collection itself - remove the old entry and insert a new one at the same position:

It looks like the interop assemblies were generated improperly by tlbimp at the certain point. You can find that assembly at \obj\Debug\netcoreapp3.1\Interop.Microsoft.Office.Interop.PowerPoint.dll.

To re-generate it properly, you need to do the following:

1. Remove the reference to "Microsoft PowerPoint 16.0 Object Library". Clean and rebuild the project. You may also try unloading the project and removing the bin and obj folders manually at this point.
2. Add references to both "Microsoft 15.0 Object Library" and "Microsoft 16.0 Object Library".
3. Add back reference to "Microsoft PowerPoint 16.0 Object Library", and clean and rebuild the project once more.

After performing these steps, my .NET Core 3.1 WinForms project was compiled successfully.

Here are the contents of the .csproj file in my case:

Begins tracking the given entity and entries reachable from the given entity using >the Modified state by default, but see below for cases when a different state will >be used.

Generally, no database interaction will be performed until SaveChanges() is called.

My guess is, that the Account is tracked until the changes are saved.

Possibly a bug, as mentioned in the other answer, meanwhile, as a workaround you may want to create a VS extension that adds the command to Solution explorer, then set the visibility rule for .cs files. Then in the action of the command, find the selected item and open it with code editor.

Add a button to solution explorer to open .cs files in code editor

This extension adds a toolbar button to the Solution Explore which will be visible, only if you choose a C# file, and when you click on it, it opens the file in code editor:

You can download or clone the solution here:

• Clone r-aghaei/SolutionExplorerViewCodeButton
• master.zip

Here is the step by step guide on creating this extension:

1. Add new project and choose 'VSIX Project' and leave the default name.
   Please note: To have this project type, you need to install 'Visual Studio extension development' when installing/modifying VS installation.

2. Add new item and choose 'Command' which is under 'Extensibility' group.

3. Open 'VSIXProject1Package.cs' file and add the following line of code to the class:

This is a similar problem to how-to-compress-log-files-older-than-30-days-in-windows.

The ArchiveOldLogs.ps1 script will preserve folder structure without the need for intermediate copying.

You can change the -Filter parameter to exclude certain files by name rather than date:

It all comes down to your requirements really. There is no silver bullet to this.

I must admit I didn't really know the settings (designer) file that you mentioned. I can tell that that's not a thing (as far as I know) in Xamarin or .NET MAUI. Probably also because there is the concept of a sandbox in mobile apps that is less a thing on desktop apps. So the location where things are saved are a bit more important.

In the comments there are already a couple of great suggestions to get you started. If your requirement is to just save simple types (string, bool, int, etc.) then the Essentials Preferences API should work just fine. I think under the hood that just serializes to a json file and stores it somewhere. Essentials is indeed already part of .NET MAUI at this time.

Xamarin.Forms used to have their own Properties, which is I think a more common concept in .NET applications, but I think the Essentials way is better.

If you want to save more complex things you might want to consider using a local database like SQLite or just roll your own and serialize your settings and save that somewhere, preferably with the Essentials FileSystem Helpers.

One thing to note here, and that is where the value of these libraries come in, is where you save the settings. Do you want the settings to be backed up to a cloud service so if survives a reinstall of the app? Or even an install of the same app on a new phone? Or do you then just want to reset the whole state and don't care about it.

If you figure that out, the rest is up to you! Hope this helps.

Use FileSystemWatcher to monitor the file change and then update that Listbox in the OnChanged event handler