Comments for Coding Cockerel

Comment on Automating the build with MSBuild (part two) by 1

Fri, 18 May 2012 16:49:36 +0000

-1′

Comment on Automating the build with MSBuild by Patrick

Patrick — Tue, 24 Apr 2012 12:59:04 +0000

Sorry, posting again because it didn’t allowed me to post tags.

Excellent article, thank you! I used the above code in the csproj file by just changing the BinFiles node to:

BinFiles Include=”$(OutputPath)\*.*”

And adding the Target as a Dependency in the following Target:

Target Name=”BeforeBuild” DependsOnTargets=”Clean”

It works really well.

Cheers,
Patrick.

Comment on Automating the build with MSBuild by Patrick

Patrick — Tue, 24 Apr 2012 12:57:50 +0000

Excellent article, thank you! I used the above code in the csproj file by just changing the BinFiles node to:

And adding the Target as a Dependency in the following Target:

It works really well.

Cheers,
Patrick.

Comment on Automating the build with MSBuild (part three) by ktata

ktata — Wed, 21 Mar 2012 15:34:22 +0000

Great Article, Thank you very much.
I am trying to execute Part 3 and getting error on creating virtual directory.
Error: Index was out of range. must be non-negative and less than the size of the collection.

Please let me know if some one know the solutions.

I am using IIS 7 on windows7.

Thanks in advance.

Comment on Add logging to your application using log4net by episerver

episerver — Sat, 11 Feb 2012 04:22:09 +0000

episerver…

[...]Add logging to your application using log4net – Coding Cockerel[...]…

Comment on How to publish a web site with MSBuild by MSBuild by jayempee - Pearltrees

MSBuild by jayempee - Pearltrees — Mon, 05 Dec 2011 12:06:44 +0000

[...] How to publish a web site with MSBuild – Coding Cockerel In part two of my MSBuild tutorial I needed to find a way to call Visual Studio’s Publish Web Site feature from MSBuild. Much trawling of the interweb failed to find anything of use, so in the end I had to produce my own target which copied the relevant files into the output folder. The problem with this approach is that it only works for files of type dll, aspx or config. [...]

Comment on How to publish a web site with MSBuild by Todd W. Powers

Todd W. Powers — Tue, 20 Sep 2011 01:29:09 +0000

I was struggling with the same error (MSB4057: The target “_CopyWebApplication” does not exist in the project.

Yes. I was using a Web Application Project (not a web site).

I was baffled because I had one project that worked, and one that did not. So I sat down with ExamDiffPro and went to work comparing the project files. What I found was the section of build target includes at the bottom of the project files were different.

One project (that was working) was created using a newer version of Visual Studio. The other one (that was NOT working) was created years ago and has been upgraded over the years, to the current version I am working with. The upgraded project, evidently didn’t get upgraded with the new build targets as newer versions of Visual Studio became available.

At the bottom of the project file which was working, I found the following:

The second import line was NOT in the project which was causing problems.

I simply copied the import from the working file, and pasted it in the relative location in the non-working file, and viola!

While this is not a direct solution to the initial problem defined in this thread, I hope this helps some of the other people that stumbled across this thread, looking for similar issues, only with actual Web Application Projects.

Comment on Automating the build with MSBuild (part three) by Zonghe

Zonghe — Wed, 02 Mar 2011 16:22:32 +0000

Superb series for a MSBuild crash course. Thanks a million~!

Comment on Automating the build with MSBuild (part three) by Sunny

Sunny — Tue, 28 Dec 2010 21:19:30 +0000

Very nice article. I am quite new to msbuild scripts but u made it quite simple.

Comment on Automating the build with MSBuild by codingcockerel

codingcockerel — Tue, 14 Dec 2010 20:34:50 +0000

Andy, I’m not familiar with LaTeX but if you just want to call programs from the command line then MSBuild can do that with the Exec command. In theory what you want to do should be achievable.