Update AssemblyInfo files failes for *.vb files

[MrHinsh]

When using the GitVersion Task for VSTS the following error occurs on VB projects:

This is due to the c# assembly info being added..

Workaround: Disable the GitVersion task and build succeeds

[gep13]

@MrHinsh can you confirm what version of GitVersion you are using within that Build Step? Thanks!

[MrHinsh]

I am using 3.5.1 from https://marketplace.visualstudio.com/items?itemName=gittools.gitversion

[apmorton]

FWIW, I am building our VB.net project on TFS, but using the msbuild task to update assembly info - not the marketplace extension.

Also, I am using 3.5.2

[asbjornu]

@MrHinsh, @apmorton Can you please try out the just released version 3.5.4 and see if that helps in any way?

[MrHinsh]

Can you update https://marketplace.visualstudio.com/items?itemName=gittools.gitversion so that I can try it!

[asbjornu]

@pascalberger Is this something you can help out with? I know absolutely zilch about VSTS. 😄

[MrHinsh]

You should get that as part of your automated DevOps pipeline ;)

[asbjornu]

@MrHinsh We've agreed on an outline for a new build process which will hopefully automate everything. 😃

[pascalberger]

Unfortunately VSTS throws an error that I don't have permissions to upload. Therefore it seems like we have to wait until tomorrow that @JakeGinnivan can have a look.

[JakeGinnivan]

Have pushed the update.

@MrHinsh unfortunately the way appveyor does it's deployments means we can't have a pipeline to vsts. We need to either switch our build system or we need to rejig how we are doing builds/releases. I'm going to sit down with @gep13 at NDC Oslo and sort it out.

[MrHinsh]

I am also speaking at NDC Oslo, maybe we can catch up! I'll also just leave this here: https://nkdagility.com/open-source-vsts-tfs-github-better-devops/

[JakeGinnivan]

Yeah that would be good, didn't get a chance last MVP Summit.

Not a bad idea using vsts as your build for github. Two quick q's.

Is there an easy way to get VSTS to publish build results back to github PRs? And is it possible to make the builds public? (if it publishes results the link will require auth, not a huge issue just wondering)

All I know is I need a better way to release my OSS stuff, AppVeyor said there was improvements coming to deployment about 12 months ago and I was waiting but doubt it will happen.

[MrHinsh]

I publish the build results as a release back to GitHub. Then I use Release Management to pull the output of the build and deploy it to Nuget / VSTS...

I use 4 builds... Two to do the sync 😀, then I have one in VSTS that protects MASTER on GitHub, and another that protects MASTER on VSTS. That way I can have a pull request on either side.

I use VSTS as the master repo, but if you use GitHub as the master then all you need is to Build in VSTS from GitHub and publish out, or use RM to do that...

[c0bra]

@asbjornu I have 3.5.4 and am currently experiencing this issue.