Can AssemblyInfo patching work for only specific files
So like for example I got like 7~8 .NET (C# assemblies), some of them must be a separate version than what my main projects are. I only want to patch the AssemblyInfo.cs files to the main projects, not the non main which are in this case plugins (5 of the) loaded by a core dll which is then loaded by the main windows forms exe that both share the same version. The other 2 assemblies are non-versioned and are just used for build (like getting information from git or for doing the actual zipping of artifacts because I want it to also zip locally even outsize of AppVeyor. So doing a patch on only 2 of the AssemblyInfo.cs files on the projects might be helpful.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Ilya Finkelshte... on 03 Jun, 2018 07:05 AM
You can share assemblyinfo file between projects you need to patch and patch only that file. This file can have different name as well.
Some helpful info:
https://stackoverflow.com/questions/6771694/shared-assemblyinfo-for...
https://blogs.msdn.microsoft.com/jjameson/2009/04/03/shared-assembl...
2 Posted by seandhunt_7 on 08 Jun, 2018 02:24 AM
Well unrelated but apperently if I call rc.exe on my laptop in a c# project it works but apperently in AppVeyor it fails under the default build with msbuild on the sln. You guys might want to add rc.exe to the path on the VS2017 boxes.
Ilya Finkelshteyn closed this discussion on 27 Aug, 2018 08:06 AM.