Yan Cui
I help clients go faster for less using serverless technologies.
This article is brought to you by
The real-time data platform that empowers developers to build innovative products faster and more reliably than ever before.
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!
Whenever you’re ready, here are 4 ways I can help you:
- Production-Ready Serverless: Join 20+ AWS Heroes & Community Builders and 1000+ other students in levelling up your serverless game. This is your one-stop shop for quickly levelling up your serverless skills.
- Do you want to know how to test serverless architectures with a fast dev & test loop? Check out my latest course, Testing Serverless Architectures and learn the smart way to test serverless.
- I help clients launch product ideas, improve their development processes and upskill their teams. If you’d like to work together, then let’s get in touch.
- Join my community on Discord, ask questions, and join the discussion on all things AWS and Serverless.
Pingback: ClickOnce deployment using TeamCity (without getting too dirty) | Robert Folkesson – blog
Pingback: ClickOnce deployment using TeamCity (without getting too dirty) | Robert Folkesson – blog