So often when you are working on a solution with multiple projects you will have to change the contents of the AssemblyInfo.cs file for each project so the DLLs show the correct company, trademark, and most importantly version numbers. This is a very laborious task and chances are you might have been wondering how you can put the common settings in one file whilst leaving you free to use the AssemblyInfo.cs file in the project for project-specific settings.
Well, the solution is simple really, you can create a file, say SharedAssemblyInfo.cs, at the solution’s root directory and put all the common settings there. Then, every time you want to make use of the common settings, just right-click on your project and Add an Exiting Item…, browse to the SharedAssemblyInfo.cs, and make sure you choose to Add As Link.
Once you’re done, you will see the SharedAssemblyInfo.cs in your project, along with a shortcut label:
Now you can safely remove all the common settings from the project’s AssemblyInfo.cs!
Enjoy what you’re reading? Subscribe to my newsletter and get more content on AWS and serverless technologies delivered straight to your inbox.
I’m an AWS Serverless Hero and the author of Production-Ready Serverless. I have run production workload at scale in AWS for nearly 10 years and I have been an architect or principal engineer with a variety of industries ranging from banking, e-commerce, sports streaming to mobile gaming. I currently work as an independent consultant focused on AWS and serverless.
In this course, we’ll cover everything you need to know to use AWS Step Functions service effectively. Including basic concepts, HTTP and event triggers, activities, design patterns and best practices.
Here is a complete list of all my posts on serverless and AWS Lambda. In the meantime, here are a few of my most popular blog posts.
- Lambda optimization tip – enable HTTP keep-alive
- You are thinking about serverless costs all wrong
- Many faced threats to Serverless security
- We can do better than percentile latencies
- I’m afraid you’re thinking about AWS Lambda cold starts all wrong
- Yubl’s road to Serverless
- AWS Lambda – should you have few monolithic functions or many single-purposed functions?
- AWS Lambda – compare coldstart time with different languages, memory and code sizes
- Guys, we’re doing pagination wrong