SDC Tasks Library

New Post: SourceTfs.Checkout Multiple Files

mikeFourie — Sat, 05 Jul 2008 09:51:40 GMT

You should be able to accomplish what you want to do with the existing tasks and batching, e.g.

</ItemGroup>

<SourceTfs.Checkout Path="%(AssemblyInfoFiles.Identity)" TfsVersion="2008" WorkingDirectory="YOURROOTPATH"/>

</Target>

New Post: Remote deploy authentication issue

mikeFourie — Fri, 04 Jul 2008 17:08:48 GMT

Hi Richard, I believe Greg.Forsythe has answered your question in the post you included above. Let me know if you still have any issues.<o:p></o:p>

Mike

New Post: Main point of assembly and build number synchronization?

mikeFourie — Fri, 04 Jul 2008 17:05:40 GMT

Hi, apologies for the delay in replying...

Build number / assembly number synchronisation is only relevant on the build server, however you a can use the TFS tasks or other tasks to sync changes to the server. It doesn’t matter if your fellow developers have a different of the assemblyinfo file, it matters that they have the latest version of the relevant code base. If you haven't read it yet, take a read of this post: http://freetodev.spaces.live.com/blog/cns!EC3C8F2028D842D5!404.entry, for some thoughts on versioning files in TFS (actually applies in general).

Mike

New Post: Application Pool Managed Pipeline mode

mieliespoor — Wed, 02 Jul 2008 18:36:05 GMT

O ok. I had a quick look and we only need to get the "ManagedPipelineMode" property. I have quickly looked at adding that to the the task, but because it is a IIS 7 property, I thought that I would add a Web7 namespace for the IIS 7 specific tasks.

I didn't have that much of time, but I will finish it during the week and test it. When I finished testing it, I will send it through then you can decide if you would want to test it and include it in the next release.

New Post: Remote deploy authentication issue

RichardHallgren — Wed, 02 Jul 2008 07:39:22 GMT

Hi,

I'm developing on a virtual machine that I run on my local host. I then have SDC based scripts that builds the solution. As long as I'm on my development machine everything works fine. When I however try to build to the test server things start to break. In the below example I've used a domain user that's a admin user and runs the BizTalk process on test.

<BizTalk2006.Application.Exists
    Application="MyApplication"
    Server="xxx.xxx.xxx.xxx"
    Database="BizTalkMgmtDb"
    UserName="domain\DomainUserOnTheTestmachine?"
    Password="PasswordForTheAboveUser">
    <Output TaskParameter="DoesExist" PropertyName="ApplicationExists" />
</BizTalk2006.Application.Exists>

When I however examine the event viewer on the test machine I see a Failure Audit log event showing on the user that runs the process on my development machine and not the user I defined in the script (doesn't matter if I define a local user on the test machine or a domain user, it's still the user running the build script). I use Check Point VPN to authenticate myself to the server.

My feeling right not is that the username and password doesn't get sent ... I'm sure that isn't the case but what am I missing here ...

I've also posted the same question here: http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=3557548&SiteID=1

Thanks in advance!

Richard

New Post: Main point of assembly and build number synchronization?

Juzzzt — Tue, 01 Jul 2008 16:08:11 GMT

Sure. Point of question is:
I think that only changing of local (which is on BuildMachine) AssemblyInfo.cs file and keeping without changing AssemblyInfo.cs file that located in SourceControl is not correct. Microsoft.Sdc.Task contains tools only for modify local file. Why shouldn't we update it everywhere.
I might be wrong in my argumentation cause it's new for me.

mikeFourie wrote:
Hi, could you elaborate on your question / concern?

New Post: SourceTfs.Checkout Multiple Files

Kyndig — Tue, 01 Jul 2008 15:34:44 GMT

Thanks for the link. I found it rather interesting and will keep it in mind if we ever switch to having TFS run the builds instead of CC.NET. Also if needed I would be interested in working on some of the TFS tasks if the original author is no longer available as I could see the use of a undo-checkout and a few other items that would be nice.

New Post: Main point of assembly and build number synchronization?

mikeFourie — Tue, 01 Jul 2008 12:48:44 GMT

Hi, could you elaborate on your question / concern?

New Post: Main point of assembly and build number synchronization?

Juzzzt — Tue, 01 Jul 2008 11:06:26 GMT

What's the main point of assembly and build number synchronization if new AssemblyInfos.cs files haven't been checkedIn in TFS? Everyone who will download project after you from TFS will not notice assemblyNumber changes.

New Post: SourceTfs.Checkout Multiple Files

mikeFourie — Mon, 30 Jun 2008 22:01:59 GMT

I'm not in contact with the author of the task any more, so I can't give you any historical reason, however I think you raise a perfectly valid point. You've actually highlighted a general flaw throughout the SDC Tasks Library though, where many tasks would be better written using ITaskItem. It's something that is being looked at for a derivative of the library.

On a side note, please take a read of this post: http://freetodev.spaces.live.com/blog/cns!EC3C8F2028D842D5!404.entry, for some thoughts on versioning files in TFS.

Thanks for the feedback.

Mike

New Post: SourceTfs.Checkout Multiple Files

Kyndig — Mon, 30 Jun 2008 19:56:18 GMT

I was wondering why the Path property for Checkout and then hence Checkin was set up as a string instead of ITaskItem[]? The string only allows for specifying a single file or folder. I have the need to update all the assembly info files in our solution with each CC.NET build so I wanted to be able to just take the AssemblyInfoFiles item I had created as follows:

    <ItemGroup>
        <AssemblyInfoFiles Include="**\AssemblyInfo.*"/>
    </ItemGroup>

and pass it into the SourceTfs.Checkout task to check them out. This doesn't work because as a string property it isn't broken up. As such I wrote my own custom task based on the SDC task that replaces the Path property type with ITaskItem[] and then iteratively calls the previous Execute code passing each item as a new Path into the method. I also did the same for the CheckIn. This may be worth changing in the main codebase as even if a user is passing in a string it should translate it to a 1 length array of ITaskItem.

New Post: Application Pool Managed Pipeline mode

mikeFourie — Mon, 30 Jun 2008 14:37:57 GMT

The current Web tasks are not tested or intended for use with IIS7.

New Post: Application Pool Managed Pipeline mode

mieliespoor — Mon, 30 Jun 2008 14:08:34 GMT

Hi there,

I don't know if I just missed it but when I create application pools in IIS 7, I need to manually set the managed pipeline mode from "Classic" to "Integrated". Because of some reason my Services doesn't work in the classic mode so is it possible to include an attribute for the Web.AppPool.CreateAppPool task to include this so when can set this when we create the AppPool? I will have a look tomorrow and see if I can get the code to do that. If possible I will post it.

Thanks,

Marais

Source code checked in, #18813

mikeFourie — Tue, 24 Jun 2008 21:48:59 GMT

SourceTfs.LabelSync: Fix to support spaces in path.

New Post: Web.WebSite.Start

mikeFourie — Tue, 24 Jun 2008 20:36:30 GMT

<Web.WebSite.Start Description="YOURWEBSITENAME" MachineName="YOURREMOTEMACHINENAME"/>

bxyoung wrote:
I'd like to use Web.WebSite.Start to reset a website on a remote computer. Is this possible? If so how?

New Post: Web.WebSite.Start

bxyoung — Tue, 24 Jun 2008 20:06:56 GMT

I'd like to use Web.WebSite.Start to reset a website on a remote computer. Is this possible? If so how?

New Post: VersionNumber.Parse not available

mikeFourie — Sat, 14 Jun 2008 07:52:36 GMT

Thanks. Logged and fixed. http://www.codeplex.com/sdctasks/WorkItem/View.aspx?WorkItemId=10338

myost wrote:
It appears that the VersionNumber.Parse function (that is listed in the documentation) is missing from the .tasks file. After adding an entry for that function, it appears to work.

Closed Issue: VersionNumber.Parse not available

mikeFourie — Sat, 14 Jun 2008 07:51:42 GMT

"It appears that the VersionNumber.Parse function (that is listed in the documentation) is missing from the .tasks file. After adding an entry for that function, it appears to work." --- reported by http://www.codeplex.com/site/users/view/myost

Source code checked in, #18651

mikeFourie — Sat, 14 Jun 2008 07:51:41 GMT

Micrsoft.Sdc.Common.Tasks: Added VersionNumber.Parse. Resolves 10338

Created Issue: VersionNumber.Parse not available

mikeFourie — Sat, 14 Jun 2008 07:47:16 GMT