I researched further and found that I was confusing website designs with web application projects. This is what I found:
Web Application Projects
- Contains assembly information through applications (hidden AssemblyInfo file)
- Creates a production site after compilation
Website Projects
- May contain assembly information through the AssemblyInfo file in the App_Code folder
- Creates a working site in place
Web Application Projects
- Copy the AssemblyInfo file only from the web application project (I tested this)
CrusieControl.NET - SVNLabeller
- You can only overwrite the version number in the AssemblyInfo file in the web application project
Thus, I will use web application projects in the future. I used to use website designs when they worked on the spot, and we just copied them to the Live Server (I know this is bad - thatβs why I ask all these questions in an attempt to improve our development environment).
This answer is my note from further research, which I consider the goal of Stack Overflow. If someone wants to change the question to something more suitable for my answer, I understand - I will try to tag myself again.
Also, if I missed the mark with my explanation, please tell me!
Greetings
EDIT
After further research, it turns out that merging assemblies causes problems with web deployment projects and web application projects. The only way to make it work is to name the assemblies in different ways, which leaves me with 1 assembly with version information and 1 assembly with my manifest information (bearing in mind that my version information comes from SVNLabeller). This is not what I want. So now I go back to website projects and find that I can manually edit the .wdproj file to add an additional assembly, this is a shame that I cannot do with Visual Studio, but this is the best solution I can come up with for Now.
David A Gibson
source share