Hello,

Thank you for the project. In the end, the main problem was not the dot, but the space character after the dot. But that's our problem, the directory name should have been sanitized. And it is now fixed.

Please rebuild with QuickOPC 5.71.272.1 (or later), which is now on our Web page, and www.nuget.org .

Note: Some (unrelated) FirstChanceException-s still happen, but that is generally OK: They just indicate that an exception has been thrown, but as long as it has been handled internally, there is no issue. I understand that attaching the event handler to FirstChanceException is a handy tool to discover some hidden problems, though.

Many thanks for reporting the problem and providing the details, it was a "good catch" and I am glad it was spotted and the cause identified.

Best regards

Hello,

The standalone example project is attached to this reply.

System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\Admin\AppData\Roaming\AMI International, S.A.P.I. de C.V. \QuickOPC_Case\1.0.0.0'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
System.IO.DirectoryNotFoundException: C:\Users\Admin\AppData\Roaming\AMI International, S.A.P.I. de C.V. \QuickOPC_Case\1.0.0.0\
at Microsoft.Extensions.FileProviders.PhysicalFileProvider..ctor(String root, ExclusionFilters filters)
System.NullReferenceException: Object reference not set to an instance of an object.
at OpcLabs.BaseLib.Extensions.FileProviders.Implementation.OnDemandWritableFileProvider.GetWritableFileInfo(String subpath)
System.NullReferenceException: Object reference not set to an instance of an object.
at OpcLabs.BaseLib.Extensions.FileProviders.Implementation.OnDemandWritableFileProvider.GetWritableFileInfo(String subpath)
at OpcLabs.BaseLib.Internal.ThreadBackground`1.<>c__DisplayClass1_0.<.ctor>b__0(Object obj)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart(Object obj)

Best regards,
IRuiz

Hello,

I would like to have a reproducible scenario (project) from you. All our own tools use "CODE Consulting and Development, s.r.o.", with the dot at the end, and there is no problem (apparently the system strips off the final dot). So, even if the dot is not fully correct (Windows allow it as such, in the API and the file system, but not in the Shell), there must be something else that causes the problem or contributes to it.

Note: We fully intend to fix this, by sanitizing the company name. I just want to have full understanding of what is involved, before we do that.

Best regards

Follow up, it seems like the library is using the assembly company name for the folder path, but you cannot end a folder name with a dot and the library do use the final dot inside the directory path.

Hello, I recently upgraded NuGet from 5.70.1202 to 5.71.256, all the projects referencing this NuGet are now throwing upon start and closing.

All projects target .NET 4.8.



Any help would be appreciated.

Regards,
IRuiz