I often write UWP software. Several techniques are adopted to make them stable and easy to extend, but when I try to release them, the following error sometimes happened…
2> CSC : error CS8002: Referenced assembly 'Microsoft.Xaml.Interactivity, Version=2.0.1.0, Culture=neutral, PublicKeyToken=null' does not have a strong name.
The reason why this error happens is that this nuget package hasn’t been signed. Werner van Deventer kindly has developed .NET Assembly Strong-Name Signer, which is very useful for us to attach a personal signature to an unsigned dll file. But not all unsigned nuget package can be dealt with by the .NET Assembly Strong-Name Signer. So I sometimes gave up using them or decided to use a software with debug mode… I wonder what to do if I can’t deal with the nuget packages perfectly that are useful but have not been signed correctly.
Building nuget packages from the source codes is one option. But when I tried to get and build Microsoft.Toolkit, the document for building and contributing it isn’t so understandable, so I often wondered what to do next to get a self-built package. And your Visual Studio hangs in minutes to write some configuration files even if you change a trivial configuration. How mush does it cost me when I try to implement a small functionality? That’s why I sometimes decide to remove some small functions in my UWP applications. Are there any good practices and time-effective ways when I’m developing an UWP application? I want to write a useful and UWP application, not to only build it.