snk | 🟩⬜ Generates a snake game from a github user contributions graph and output a screen capture as ani | Animation library

I'm not asking where the path to the strong name key goes. It should be obvious. I'm asking how the path expression should look like, knowing pretty much everything about operating system path specifications.

The GitHub project is a Visual Studio 2022 solution consisting of over 20 .NET 6.0 C# projects. Most of the projects are intended to be published as separate NuGet packages.

With those things out of the way, the details.

The path to the key should be placed in the project file. And here's my concern: I can specify 2 kind of paths: absolute and relative. The relative will break when I move my project. The absolute will break when I move the key.

Absolute path like "D:\Source\Keys\MyKey.snk" will also break when I change the drive letter, the Windows assigns a different drive letter to a removable drive etc.

Unless I pass the path like "\Source\Keys\MyKey.snk". It seems like the most elegant and best solution, if only Visual Studio allowed that to work. But it doesn't. I guess it resolves it as "C:\Source\Keys\MyKey.snk" because why not, if it's installed in "C:\...".

So, either the ugly path with the drive letter, or the ugly relative path. My exact question is is there a third option? Maybe IDK, using an environment variable, a Visual Studio configured internal variable or something like that?

For now I stick to the relative path. Then there's another issue. If someone pulls the GitHub project, it won't compile complaining on the missing keys. Of course they can remove assembly signing and then it would work.

Is there another way?

So the current state of my GitHub project is "strong names by default / relative key paths", it allows me to focus on the coding without unnecessary distraction when pushing or publishing the code changes. But if there was a better solution for the keys, I'm just curious.

I have a DLL based on netcoreapp3.1. The DLL references the NuGet package Microsoft.Extensions.Configuration.Json version 5.0.0. If I deploy the DLL to another PC where VisualStudio is not installed and try to access it from a third party program, I get the error:

I am calling COM object (written in C#) from COBOL. But when I try to call it, I receive this error:

I have been trying to upload my project into Github. Github has uploaded everything apart from my client app. Im new to source control and I can't work out why or what I am missing.

Here is my folder structure in VS Code:

Here is how Github has uploaded it:

Github has ignored the project. The project isn't in the gitignore file either.

here is my gitignore:

I'm interested in compiling Roslyn myself to use his internal classes like RegexParser and others.

And I should also be able to sign the files, to use them inside a VSTO plugin.

I saw here a tutorial on how to sign Roslyn, but it's an old tutorial that no longer fits Roslyn today.

I downloaded and built the code from here But it was signed by:

I'm trying to export Google Cloud Organization's logs to the _Default log bucket from another project. It seems impossible right now. There's not a single clue or error telling me why. What I've tried so far is to:

• Export to pub/sub topic
• Export to custom GCS bucket
• Export to _Default logging bucket from another project. // THIS is the case I'd lake to work on.
• Export to custom logging bucket from another project.

The same behavior is observed in all those cases: no logs are exported at all.

I'm using Terraform for this task and everything seems fine in configurations. I'm giving also the correct IAM permissinons to the service account writer identity:

This question is an extension of the following:

• Should each project being signed with a separate Strong Name Key (.snk)?
• snk vs. code signing certificate
• Any reason to ship .snk file with the project sources?
• https://docs.microsoft.com/en-us/dotnet/standard/assembly/enhanced-strong-naming

I am looking at Strong Naming a custom assembly along with code signing it and have read various SO posts (see above) and the MSDN. I understand the following:

1. Strong naming an assembly without a password creates an SNK file and only identifies the publisher of the assembly so that it can be deployed to the GAC and mitigate the so-call DLL Hell caused by identically named assemblies from different publishers.
2. Strong naming an assembly with a password adds code signing to an assembly and creates a PFX file, instead of an SNK file. This both identifies the publisher and verifies that the code has not been tampered with. Note: This file can either be created, and thus imported, by a trusted certificate authority like Verisign and Digicert or it can be a self-signed certificate created within the organization. Self-creating a PFX is the same step as creating a Strong Named assembly, but you just add a password to it.
3. Enhanced Strong Naming seems a bit of a mystery to me. It involves creating a Strong Named SNK file (i.e., no password) and then extracting the private key from it. It seems to only be for allowing the migration from deprecated hashing algorithms.

I understand 2 to be a logical extension of 1. Is my understand above correct? But, what is the difference between 2 and 3 above? Does 3 have any advantage over 1 or is it just a way to allow migration across algorithms only? Said differently, I imagine the 2 and 3 exist for distinct reasons; what is that reason/implementation?

Also discussed at:

https://verificationacademy.com/forums/systemverilog/parameterizing-bit-widths-fields-packed-struct-so-modules-can-infer-bit-width-if-used-port-map-virtual-interface-interface-compile-time-configured-struct-bit-width

https://forums.xilinx.com/t5/Synthesis/Parameterizing-the-Bit-Widths-of-fields-in-a-packed-struct-so/td-p/1191678

I am having trouble accomplishing my intent in SystemVerilog trying to use the latest language features to make my code more elegant and less verbose. For synthesis**

I would like to accomplish the following:

• be able to parameterize the bit widths of fields in a packed struct that I want to define ... I have attempted to accomplish this using a parameterized interface construct
• I would like for modules with that parameterized interface as an INPUT to the module to be able to infer the bit width of a field inside that packed struct defined inside the interface

I have been mostly successful in past experiments but I have run into an issue.

Please see the following simple interface definition:

I have been facing this problem with git in which I am trying to upload .mp4 files in a subdirectory of wwwroot/ but whenever I am writing git status, they won't appear.

The new video files are located inside wwwroot/Content/Videos/ZoomEspecialista/ This problem has never occured before. I have uploaded maybe 10-15 new .mp4 files.

Regardless of that, in my .gitignore file, I am not excluding the folder which contains these .mp4 files. I have checked multiple times to see if there is something, but I think the problem lies somewhere else. If anyone has any idea on how to tackle this issue, it would be superbly appreciating. Thanks!

The only thing I get from doing a git status is this despite of having uploaded my files to that subdirectory:

EDIT 2: Here is my .gitignore file: