VSIX update needed!

Sep 20, 2010 at 7:31 AM

FYI, David just checked in some fixes which make old builds incompatible.  So if your current bits go again the live public feed, you’ll likely get some errors.  To fix this, just sync and rebuild the latest vsix and you'll be ok :)

Sep 20, 2010 at 12:21 PM

What's the users/develpers story on updating the vsix? If you have it installed running it won't let you update. I find I always have to uninstall it, restart VS, reinstall it, restart VS. Or is it just me?

Sep 20, 2010 at 1:33 PM

It's because we're not upping the vsix version, which we will do from one public build to the next.  Once you do that, it all happens nicely on update.

Sep 20, 2010 at 2:07 PM

We need an issues to version the vsix and the nupack.exe

On Sep 20, 2010 8:34 AM, "davidebb" <notifications@codeplex.com> wrote:
> From: davidebb
>
> It's because we're not upping the vsix version, which we will do from one public build to the next. Once you do that, it all happens nicely on update.
>
>

Developer
Sep 20, 2010 at 4:27 PM

Needs to be some kind of build task that increments the version number in the vsix.manifest before building.

Sep 20, 2010 at 4:44 PM

Log an issue? Can do, just need to know what we want to use to increment the version.  In other words, how are we versioning?

____
Rob
"Be passionate in all you do"

http://devlicio.us/blogs/rob_reynolds
http://ferventcoder.com
http://twitter.com/ferventcoder

On Sep 20, 2010 11:27 AM, "dfowler" <notifications@codeplex.com> wrote:
> From: dfowler
>
> Needs to be some kind of build task that increments the version number in the vsix.manifest before building.
>
>

Sep 20, 2010 at 5:18 PM
Although you might want to be careful about auto incrementing the version number every build for the release build, of course that depends on what you base it on.

-d
Sep 20, 2010 at 5:23 PM

Yes, not a big fan of auto incrementing every time we build.  It causes unnecessary diffs, and it doesn't merge well.  I think we only need to do that between public drops.

Sep 20, 2010 at 5:38 PM

On my past projects, we have a CI build profile for "Release" that we run on demand, that versions, signs, and does stuff that is only for public releases.