Keep V3 assembly version fixed

development's Avatar


15 Apr, 2013 08:33 AM


I realize that V3 is still beta/rc, yet you encourage new users til use V3 in their projects. In other words, using V3 is no longer just for fun and for testing. Would you consider keeping V3 assembly version fixed soon? It would make things a lot easier for we plan to start using V3 in its current state...

  1. Support Staff 1 Posted by PostSharp Techn... on 15 Apr, 2013 08:46 AM

    PostSharp Technologies's Avatar

    Which problem precisely stops you from using PostSharp?

  2. 2 Posted by development on 15 Apr, 2013 08:55 AM

    development's Avatar

    The version 3 I downloaded is assembly version, while the file and product version is This indicates that if you have a new patch, the assembly version would be bumped to for example. Is this correct?

    As we are not using NuGet, any PostSharp update that we want to pick up, requires manually update of all PostSharp dll references. If the assembly version changes that is..

  3. Support Staff 3 Posted by PostSharp Techn... on 15 Apr, 2013 09:01 AM

    PostSharp Technologies's Avatar

    The last part in the version number is for the target platform (*.9 for .NET, *.3 for portable). The assembly version does not need to be equal to the file version (although in practice the first three version parts are).

    We plan to increment the version number at every build, even after the RTM. Not using NuGet is currently unsupported (this is possible but PostSharp is not optimized for this scenario). You can enter a reference without a reference number if you want, by editing your csproj file manually.

  4. 4 Posted by development on 15 Apr, 2013 09:23 AM

    development's Avatar

    Alright, we will discuss how to handle PS updates in the future. Perhaps this is a time to start using NuGet. Troubles is, that when people (developers) are nagged about updates (e.g. from NuGet) they tend to hit "update" even though a company policy is not to do so...when we have several layers that all use PostSharp we really need to run the same version. Until now, this has been easy since I am in 100% control of the DLL used...

  5. Support Staff 5 Posted by PostSharp Techn... on 15 Apr, 2013 09:30 AM

    PostSharp Technologies's Avatar

    Yep, we know about the issue (other customers complained too). We implemented a workaround to allow to use the PostSharp compiler without NuGet (most of the features of the VSX won't work), but the fact is that 3.0 is now designed for NuGet.

    If you don't want troubles during updates without NuGet, use version-independent assembly references.

  6. 6 Posted by development on 15 Apr, 2013 10:22 AM

    development's Avatar

    Thanks. I can add that setting up a local NuGet repository is quite easy, and I've just added PS V3. I would imagine that this way, I can also control when a new PS version is introduced in our setup...

  7. Support Staff 7 Posted by PostSharp Techn... on 15 Apr, 2013 10:24 AM

    PostSharp Technologies's Avatar

    This would be the best solution. The other customer had an issue because they had a large number of solutions, but the versioning issue can be solved using local repositories.


  8. 8 Posted by Joe Kuemerle on 15 Apr, 2013 03:38 PM

    Joe Kuemerle's Avatar

    Another option for self hosting NuGet is to use ProGet ( ) . With ProGet, you don't have to
    manually move packages from to your internal server, you can
    just set up a connector and filter the feed.

    If you do this you also get the feature where you only have a single
    canonical NuGet feed for developers/build servers to use so you don't
    have the headache of multiple feeds and people accidently pulling down
    the "wrong" packages from

  9. 9 Posted by development on 16 Apr, 2013 09:10 AM

    development's Avatar

    Thanks Joe, I'll definately have a look at that too.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? 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