PSMinIO Developer
2974ead76e
Key Achievements: - Downgraded to MinIO 4.0.7 for PowerShell compatibility (eliminated async/await issues) - Fixed file handle leaks in upload operations (using explicit FileStream management) - Implemented clean logging (timestamps without redundant prefixes) - Fixed automatic session variable management (Connect-MinIO stores, cmdlets retrieve) - Removed duplicate certificate parameters (kept only SkipCertificateValidation) - Fixed all 'Folder' alias conflicts across cmdlets - Added correct System.Runtime.CompilerServices.Unsafe.dll version (4.5.3) Working Features: - Connection management (automatic + explicit override) - Bucket operations (list, create, remove) - File upload/download (with proper handle release) - Progress tracking and speed reporting - Clean verbose logging with timestamps Known Issue: - Chunked operations have threading violations (PowerShell cmdlet methods called from background threads) - Regular operations work perfectly, chunked operations need threading architecture fix Test Results: - 3.71GB Windows install.wim file tested - Regular upload/download: Working - File handles: No leaks, immediate deletion possible - Session management: Automatic connection storage/retrieval - Chunked operations: Threading violations need fix
3.3 KiB
System.Runtime.CompilerServices.Unsafe Polyfill for .NET Framework 4.0
Provides the System.Runtime.CompilerServices.Unsafe class, which provides generic, low-level functionality for manipulating pointers.
Commonly Used Types:
- System.Runtime.CompilerServices.Unsafe
This package adds support for System.Runtime.CompilerServices.Unsafe on .NET Framework 4.0.
This is a compilation using the System.Runtime.CompilerServices.Unsafe source code from .NET Core 6.0.28. All tests are passing.
This is not meant to be an upgrade to System.Runtime.CompilerServices.Unsafe 6.0.0, it is simply to add support on the net40 target for all of the existing APIs in System.Runtime.CompilerServices.Unsafe 6.0.0. It is recommended to use the official release of System.Runtime.CompilerServices.Unsafe on newer versions of .NET.
Interop with System.Runtime.CompilerServices.Unsafe on Targets > net40
Since the runtime for net40 hasn't been supported for many years, most likely you will be using a newer runtime with this library. But you may be interoperating with other components that target System.Runtime.CompilerServices.Unsafe, which will cause type collisions by default.
In this case, it is recommended to remove System.Runtime.CompilerServices.Unsafe from compilation and add NetFx.System.Runtime.CompilerServices.Unsafe in its place. Add the following to your .csproj or .vbproj file. This example is for using net452.
<ItemGroup Condition=" '$(TargetFramework)' == 'net452' ">
<!-- ExcludeAssets=compile removes the dependency from being referenced.
ExcludeAssets=runtime removes the dependency from the build output. -->
<PackageReference Include="System.Runtime.CompilerServices.Unsafe"
Version="6.0.0"
ExcludeAssets="compile;runtime" />
<PackageReference Include="NetFx.System.Runtime.CompilerServices.Unsafe"
Version="4.0.0" />
</ItemGroup>
NOTE: Only SDK-style projects are supported using this method.
For transitive dependencies (that is, dependencies that are not directly referenced) that have a net40 target, consider forcing a specific target framework.
Saying Thanks
If you find this library to be useful, please star us on GitHub and consider a sponsorship so we can continue bringing you great free tools like this one. It really would make a big difference!