Missing [assembly: AssemblyMetadata("Serviceable", "True")]
See original GitHub issueIf a project is serviceable and can potentially run on .NET Framework (i.e. targets net472, netstandard2.0, etc.) it should include the following assembly-level attribute.
[assembly: AssemblyMetadata("Serviceable", "True")]
cc @Eilon
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:30 (28 by maintainers)
Top Results From Across the Web
MSBuild reference for .NET SDK projects
When the GenerateAssemblyInfo value is true , package-related project properties are transformed into assembly attributes.
Read more >json - dotPeek not showing all references
As the answer to this question mentions the reason why DotPeek did not display all references was because it could not find the...
Read more >Are you missing a using directive or an assembly reference
First find out where it is: if it's in a different assembly, then you need to check that you have added that to...
Read more >Assemblies, Metadata and Manifests
The assembly's manifest contains assembly metadata that is used for resolving types and satisfying resource requests. It specifies the types and resources ...
Read more >Getting Assemblies Is Harder Than You Think In C# – .NET ...
If you try to do GetReferencedAssemblies(), starting with the GetEntryAssembly(), and there is no usage of ReferenceA, then the chain is broken, and...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ok. I guess the best way to fully understand how it works is to give it a spin! Also, I’m on FR this and next week but I’ll talk to my team and see if someone has the cycles to start working on it. I’ve included details about this in https://github.com/dotnet/arcade/issues/5631
I don’t know of any other work that would address it. We still do have several packages that are .NET Standard, and our other servicing work is only related to reference assemblies, where I assume this needs to be in reference asssemblies.