MSBuild Extension Pack

Patch Applied: #14408

mikeFourie — Mon, 20 May 2013 20:41:50 GMT

mikeFourie has applied patch #14408.

Comment:
https://msbuildextensionpack.codeplex.com/SourceControl/changeset/83743

Patch Applied: #14384

mikeFourie — Mon, 20 May 2013 20:41:44 GMT

mikeFourie has applied patch #14384.

Comment:
https://msbuildextensionpack.codeplex.com/SourceControl/changeset/83743

Closed Feature: Add CommitMesssage property to the Svn commit action [11734]

mikeFourie — Mon, 20 May 2013 20:40:59 GMT

At present, use of the subversion commit task has a fixed message of "MsBuild".

For example, this Msbuild statement:
<MSBuild.ExtensionPack.Subversion.Svn TaskAction="Commit" Item="Somefile.cs"/>
will appear in your commit log with a commit log of just "MSBuild".

It would be nice to have the possibility to add a committ message, like this:
<MSBuild.ExtensionPack.Subversion.Svn TaskAction="Commit" Item="Somefile.cs" CommitMessage="Somefile committed by MSBuild" />

I have written this functionality, but have never worked with CodePlex before. The CSC client was troublesome, so I checked out the most recent code with Subversion. I have a Subversion-format patch. I'm attaching it to this message, and will also try to upload it as a patch in CodePlex but it probably wont accept it. The code compiles.

I can't properly test the code because I don't have Visual Studio 2012 installed.

Can anyone look at this?

Jan Brogger
Comments: Resolved with changeset 83743: Subversion\Svn.cs: Fix 11734 - Add CommitMesssage property to the Svn commit action

Source code checked in, #83743

mikeFourie — Mon, 20 May 2013 20:40:56 GMT

Subversion\Svn.cs: Fix 11734 - Add CommitMesssage property to the Svn commit action

Patch Applied: #14407

mikeFourie — Mon, 20 May 2013 20:37:33 GMT

mikeFourie has applied patch #14407.

Comment:
https://msbuildextensionpack.codeplex.com/SourceControl/changeset/83742

Patch Applied: #14400

mikeFourie — Mon, 20 May 2013 20:37:07 GMT

mikeFourie has applied patch #14400.

Comment:
https://msbuildextensionpack.codeplex.com/SourceControl/changeset/83742

Closed Feature: Error message "Invalid output from SVN tool" is too broad [11742]

mikeFourie — Mon, 20 May 2013 20:36:25 GMT

There are a number of places in the Svn.cs code that just emit "Invalid output from SVN tool". We have intermittent build failures with TeamCity. More informative error messages would help in tracking these down.

I've made a patch in Subversion patch format - submitted over at patches.
Comments: Resolved with changeset 83742: Subversion\Svn.cs: Fix 11742 - Error message "Invalid output from SVN tool" is too broad

Source code checked in, #83742

mikeFourie — Mon, 20 May 2013 20:36:23 GMT

Subversion\Svn.cs: Fix 11742 - Error message "Invalid output from SVN tool" is too broad

New Post: HttpWebRequest - set contentType for Request

gdmstow — Mon, 20 May 2013 20:35:07 GMT

Hi Mike,
The content type would default to null, so I guess leaving it at null wouldn't break existing users.

regards,
Graeme.

Edited Feature: Error message "Invalid output from SVN tool" is too broad [11742]

mikeFourie — Mon, 20 May 2013 20:32:26 GMT

New Post: HttpWebRequest - set contentType for Request

mikeFourie — Mon, 20 May 2013 19:59:29 GMT

Indeed, would you expect the default to be null or

this.ContentType = "application/x-www-form-urlencoded";

New Post: HttpWebRequest - set contentType for Request

gdmstow — Mon, 20 May 2013 15:14:21 GMT

It seems a very simple change to enable the ContentType property for ActionType=GetResponse, what do you think?

Cheers,
Graeme.

New Post: Including MSBuild.ExtensionPack.VersionNumber.targets

Srikanthgowda — Fri, 17 May 2013 05:47:15 GMT

Where can i get the exe and i dont want to generate the version by user. I want Assemblyinfotask to update the Assemblyinfo file and i would like to kno whow exactly I can do that?

New Post: Including MSBuild.ExtensionPack.VersionNumber.targets

RKDD — Fri, 17 May 2013 05:42:52 GMT

Hi,
a special Tool ChangeFileVersionInfo with up to 5 parameters was developed to change the version infos according to our special in-house version info settings.
The call is like <Exec WorkingDirectory="$(BuiltDir)" Command="".\ChangeFileVersionInfos.exe" "$(BuiltDir)" param1 param2 param3" /> and is placed between checkout and checkin commands.

New Post: Including MSBuild.ExtensionPack.VersionNumber.targets

Srikanthgowda — Fri, 17 May 2013 03:20:05 GMT

Can you please tell me which line exactly modifies the assemblyinfo file?
Since i am trying to build with the flow you explained here but version is not getting updated in the versioninfo file and checkin is happeneing without modification.

Steps following:

Added import tag
Aded code to checkout the file using script

<Exec WorkingDirectory="$(SolutionRoot)"

      Command="$(TF) checkout /recursive $(AssemblyInfoSpec)"/>

Added code to checkin the file if successful

<Exec WorkingDirectory="$(SolutionRoot)"

  Command="$(TF) checkin /comment:&quot;Auto-Build: Version Update&quot; /noprompt /override:&quot;Auto-Build: Version Update&quot; /recursive "/>

Undo the file is failure.

<Exec WorkingDirectory="$(SolutionRoot)"

      Command="$(TF) undo /noprompt /recursive $(AssemblyInfoSpec)"/>

Thanks in advance.

New Post: Extension Pack and Nuget

ludwighoff — Tue, 14 May 2013 10:57:18 GMT

Dominik

what does your root directory msbuild file do?

Reason I ask is that you could use this file (or indeed after.SOLUTIONNAME.sln.targets) to conditionally XmlPoke in the references to each csproj... (or use the MSBuild model to load up each csproj - which would probably be neater.)

If you used the latter then you could batch through the ProjectReference ItemGroup to get each csproj....

The drawback of using after.SOLUTIONNAME.sln.targets is that F5 in VS does not pick it up - it only gets picked up when you run SOLUTIONNAME.sln directly from MSBuild.

It's all a bit filthy though...

Neil

P.S. How long must we wait to finally get MSBuild solution files? :-)

New Post: Extension Pack and Nuget

rubicon_dominik — Tue, 14 May 2013 09:51:56 GMT

We've got a solution and many projects. The solution has a msbuild file on the root directory, how to correctly use the ExtensionPack nuget package without adding it to each and every project in it?

Is there some special "build project" type?

How do you handle this situation?

All the best,
D.R.

New Post: App Pool Creation in IIS 7

mikeFourie — Tue, 14 May 2013 06:50:42 GMT

Hi Greg

I cant repro this issue and comparing the code there are quite a lot of changes, but nothing that would appear to cause an issue like this. Does the task error when you run it?

Mike

New Post: App Pool Creation in IIS 7

gsuttie — Mon, 13 May 2013 13:58:15 GMT

We are creating an app pool in IIS 7

<MSBuild.ExtensionPack.Web.Iis7AppPool

  TaskAction="Create"
  AutoStart="true"
  MachineName="$(Server)"
  ManagedRuntimeVersion="v4.0"
  Name="$(WebsiteName)"
  PipelineMode="Integrated"
  MaxProcesses="1"
  IdentityType="NetworkService"
  Force="true" 
  Condition="$(AppPoolIdentity) == ''" />

This used to work in msbuildextensionpack 3.5.5 but in 4.0.7.0 I get an error in the event log stating that :-

The application '/' belonging to site '2' has an invalid AppPoolId 'Catalogue' set. Therefore, the application will be ignored.

Which means that the website isn't configured correctly (the Authentication settings are wrong)

Any ideas on what's changed or if I am missing anything?

Thanks
Greg

New Post: Using MSBuild Extension pack to Deploy Code - Need to update configuration file before MSBuild is called to compile code?

mikeFourie — Fri, 10 May 2013 12:16:03 GMT

Ok so you have a bespoke process, i.e. this isn't part of project compilation.

you could have a 2nd copy of the file with the right content and then copy that, or you could call a task to edit the file content before doing it. Again, you have options, like doing regex replace or xml editing.

See: http://www.msbuildextensionpack.com/help/4.0.7.0/?topic=html/f8c545f9-d58f-640e-3fce-b10aa158ca95.htm for replace and http://www.msbuildextensionpack.com/help/4.0.7.0/?topic=html/4009fe8c-73c1-154f-ee8c-e9fda7f5fd96.htm for xml

Mike