crystalgreen

One can easily strong name all project references that are not strongly named with the [StrongNamer](https://github.com/dsplaisted/strongnamer) tool. Just add that [nuget package](https://www.nuget.org/packages/strongnamer) to your project and it's done.

I have a similar issue. I use node with ts-node and tsconfig-paths. If my path mapping is defined in an inner tsconfig that is referenced via TS project references by...

Thanks for your answer. I guess, you would not write type info for JSON types like string, number, boolean. If one does not serialize the (primary) column type (of a...

I created a reduced version of my serializer that focuses on arrays, without class serialization support. Have a look [here](https://gist.github.com/crystalgreen/9bccb79c509ac595523f8e219b5b3ef7), maybe you can use it or at least get inspiration.

I currently do not plan to create a public library but this may change in the future. My full blown library with serialization support for classes and other JS type...

> Not only that but custom targets that depend on the `$(PkgMyLib)` property will now fail because the property is not defined. I work around this by using a condition...

I also ran into the issue (.NET 6) but found a nice way that works. According to https://docs.microsoft.com/en-us/nuget/reference/msbuild-targets#pack-target many nuspec settings have now corresponding MSBuild properties and one can pass...

I extract a 7z archive and the USAGE doc indicates it is more efficient to use `ExtractAllEntries` or `WriteAllToDirectory`. Is there another efficient way with more control over extraction?

@jdpurcell Your workaround looks promising, thanks. This issue can be closed unless you consider adding the workaround to the lib.