Comments on: Ease Versioning Multiple Assemblies by Splitting Up AssemblyInfo http://blog.darrenstokes.com/2007/12/17/ease-versioning-multiple-assemblies-by-splitting-up-assemblyinfo/ Thoughts on programming and other things Sun, 01 Aug 2010 13:17:26 -0700 http://wordpress.org/?v=2.8.4 hourly 1 By: Neil Johnson http://blog.darrenstokes.com/2007/12/17/ease-versioning-multiple-assemblies-by-splitting-up-assemblyinfo/comment-page-1/#comment-15703 Neil Johnson Tue, 08 Dec 2009 17:18:05 +0000 http://blog.darrenstokes.com/2007/12/17/ease-versioning-multiple-assemblies-by-splitting-up-assemblyinfo/#comment-15703 Great solution - also works for VB - I was wondering if linking worked in VB - and following your instructions - it does! Thanks Great solution – also works for VB – I was wondering if linking worked in VB – and following your instructions – it does!

Thanks

]]> By: Add an existing file to a project without copying it. : Visual Studio Hacks http://blog.darrenstokes.com/2007/12/17/ease-versioning-multiple-assemblies-by-splitting-up-assemblyinfo/comment-page-1/#comment-15157 Add an existing file to a project without copying it. : Visual Studio Hacks Mon, 23 Nov 2009 22:25:45 +0000 http://blog.darrenstokes.com/2007/12/17/ease-versioning-multiple-assemblies-by-splitting-up-assemblyinfo/#comment-15157 [...] A few months ago, I posted an article on my blog explaining Versioning Multiple Assemblies by changing one partial AssemblyInfo file. [...] [...] A few months ago, I posted an article on my blog explaining Versioning Multiple Assemblies by changing one partial AssemblyInfo file. [...]

]]> By: Brian http://blog.darrenstokes.com/2007/12/17/ease-versioning-multiple-assemblies-by-splitting-up-assemblyinfo/comment-page-1/#comment-6471 Brian Wed, 31 Dec 2008 01:15:21 +0000 http://blog.darrenstokes.com/2007/12/17/ease-versioning-multiple-assemblies-by-splitting-up-assemblyinfo/#comment-6471 I've found that this works if all of your projects are of the same language, but what about if you have mixed VB.NET and C#? I’ve found that this works if all of your projects are of the same language, but what about if you have mixed VB.NET and C#?

]]> By: Conrad Braam http://blog.darrenstokes.com/2007/12/17/ease-versioning-multiple-assemblies-by-splitting-up-assemblyinfo/comment-page-1/#comment-6148 Conrad Braam Fri, 19 Dec 2008 15:11:54 +0000 http://blog.darrenstokes.com/2007/12/17/ease-versioning-multiple-assemblies-by-splitting-up-assemblyinfo/#comment-6148 Great solution. I have a project with about 30 assemblies, and when I noticed the versions and Company/Product name were mostly blank and in some cases filled with well-meaning variations of the correct info (but inconsistent)... I just want to know is someone has a top-ten list of commonly broken things on large .NET and WPF projects. It would make it easier to motivate cleaning up the "broken windows" feel if the worst project baddies were ranked and shamed. Great solution. I have a project with about 30 assemblies, and when I noticed the versions and Company/Product name were mostly blank and in some cases filled with well-meaning variations of the correct info (but inconsistent)…
I just want to know is someone has a top-ten list of commonly broken things on large .NET and WPF projects. It would make it easier to motivate cleaning up the “broken windows” feel if the worst project baddies were ranked and shamed.

]]> By: Grant Palin http://blog.darrenstokes.com/2007/12/17/ease-versioning-multiple-assemblies-by-splitting-up-assemblyinfo/comment-page-1/#comment-309 Grant Palin Fri, 21 Mar 2008 01:07:49 +0000 http://blog.darrenstokes.com/2007/12/17/ease-versioning-multiple-assemblies-by-splitting-up-assemblyinfo/#comment-309 I figured as much. Nuts for the easy solution...Yet another reason to upgrade! I do have VS 2005, from the launch event a few years ago. Have only tinkered with it so far...Guess I should try moving my project over and see what happens! I figured as much. Nuts for the easy solution…Yet another reason to upgrade!

I do have VS 2005, from the launch event a few years ago. Have only tinkered with it so far…Guess I should try moving my project over and see what happens!

]]> By: Darren Stokes http://blog.darrenstokes.com/2007/12/17/ease-versioning-multiple-assemblies-by-splitting-up-assemblyinfo/comment-page-1/#comment-304 Darren Stokes Thu, 20 Mar 2008 10:37:52 +0000 http://blog.darrenstokes.com/2007/12/17/ease-versioning-multiple-assemblies-by-splitting-up-assemblyinfo/#comment-304 That must be the problem. I'm using 2005 and 2008 and it works on both of those. Microsoft must have added this functionality for web projects after 2002. That must be the problem. I’m using 2005 and 2008 and it works on both of those. Microsoft must have added this functionality for web projects after 2002.

]]> By: Grant Palin http://blog.darrenstokes.com/2007/12/17/ease-versioning-multiple-assemblies-by-splitting-up-assemblyinfo/comment-page-1/#comment-300 Grant Palin Thu, 20 Mar 2008 01:40:47 +0000 http://blog.darrenstokes.com/2007/12/17/ease-versioning-multiple-assemblies-by-splitting-up-assemblyinfo/#comment-300 I'm using VS 2002, if it matters. I don't know if the linking to web projects is possible in VS 2005/8. I’m using VS 2002, if it matters. I don’t know if the linking to web projects is possible in VS 2005/8.

]]> By: Grant Palin http://blog.darrenstokes.com/2007/12/17/ease-versioning-multiple-assemblies-by-splitting-up-assemblyinfo/comment-page-1/#comment-299 Grant Palin Thu, 20 Mar 2008 01:39:47 +0000 http://blog.darrenstokes.com/2007/12/17/ease-versioning-multiple-assemblies-by-splitting-up-assemblyinfo/#comment-299 My solution has 2 class libraries and one web project. For the libraries, the little arrow on the Add dialog shows 3 options: Open, Open With..., and Link File. For the web project, only the first two options are shown, and not the linking one. My solution has 2 class libraries and one web project. For the libraries, the little arrow on the Add dialog shows 3 options: Open, Open With…, and Link File. For the web project, only the first two options are shown, and not the linking one.

]]> By: Darren Stokes http://blog.darrenstokes.com/2007/12/17/ease-versioning-multiple-assemblies-by-splitting-up-assemblyinfo/comment-page-1/#comment-294 Darren Stokes Wed, 19 Mar 2008 10:23:03 +0000 http://blog.darrenstokes.com/2007/12/17/ease-versioning-multiple-assemblies-by-splitting-up-assemblyinfo/#comment-294 Grant, I just created a solution with a web application project and a class library project and was able to add a link to the common assemblyinfo to both and compile without a problem. I'm not sure what the problem could be. Are you getting an error? Grant,

I just created a solution with a web application project and a class library project and was able to add a link to the common assemblyinfo to both and compile without a problem.

I’m not sure what the problem could be. Are you getting an error?

]]> By: Grant Palin http://blog.darrenstokes.com/2007/12/17/ease-versioning-multiple-assemblies-by-splitting-up-assemblyinfo/comment-page-1/#comment-291 Grant Palin Wed, 19 Mar 2008 04:54:03 +0000 http://blog.darrenstokes.com/2007/12/17/ease-versioning-multiple-assemblies-by-splitting-up-assemblyinfo/#comment-291 Hey this is pretty neat. I just figured out how to get NAnt to automatically increment the number in my separate projects (3 projects in one solution) so the numbers are the same for each final assembly. But this solution seems like a tidier way to handle that. One question though, does this technique work for web projects? One of mine is a web project, and I was not able to "link" the common assembly file to it. Any suggestions? Hey this is pretty neat. I just figured out how to get NAnt to automatically increment the number in my separate projects (3 projects in one solution) so the numbers are the same for each final assembly. But this solution seems like a tidier way to handle that.

One question though, does this technique work for web projects? One of mine is a web project, and I was not able to “link” the common assembly file to it. Any suggestions?

]]>