In the visual studio command prompt, open <Drive>:\Program Files\Microsoft Visual Studio 8\Common7\IDE and run the command

tf.exe delete /lock:none /recursive “Root\SubRoot”

If you have more folders below the Subfolder SubRoot, then those also will be marked for deletion, for that /recursive is used.

Once done this, we need to checkin the pending changes, for that run the command

tf.exe checkin /recursive “Root\SubRoot”

This will checkin the pending delete changes and remove the folder from the repository and workspace.

 -Thanks

open vs 2005 or 2008 command line tool and run below command:

in 2005:
C:\Program Files\Microsoft Visual Studio 8\Common7\IDE>TFSDeleteProject.exe  /Server:MyServerName MyProjectName

in 2008:
C:\Program Files\Microsoft Visual Studio 9.0\VC>TFSDeleteProject.exe /Server:MyServerName MyProjectName

If your project name contains spaces (My Project Name), then put the Project name in double quotes (“My Project Name”)

-Thanks

So inorder to delete SSP , we need to make use of the commandline tool called stsadm

stsadm tool is located at C:\Program Files\Common Files\Microsoft Shared\web server extension\12\Bin.

Open the command prompt and navigate to the directory where stsadm tool is located and type the following command

stsadm -o deletessp -title “SharedService1″ -force

And also check in the IIS that the TFS is running with the Port 8080.

To check whether TFS is working fine ,you can browse the following webservice in the browser

http://<server>:8080/services/v1.0/serverstatus.asmx and if it shows up without error, then you should not have problem connecting TFS from remote machine

Thanks,

Sudhir

Open IIS and under Application Pools right click on Microsoft Team Foundation Server Application Pool and go to performance tab of the properties window and uncheck the check

 box next to Shutdown worker process after being idle for (time in minutes).

Go to C:\wamp\bin\apache\apache-version\conf\httpd.Conf
and look for Listen 80 and change it to Listen 82

But if you want the WAMP menu also to work, we need to make changes
to wampmanager.ini and wammanager.Tpl file at c:\wamp

In both the files search for all instances of http://localhost and
replace it with http://localhost:82

Thats It! Enjoy both IIS and WAMP on same machine

Thanks,
Sudhir

Thanks

For this, there is a work arround

You can follow below step or you can go to the original blog directly from here.

1) Download the copy of MOSS 2007 SP1    (en_office_sharepoint_server_2007_standard_and_enterprise_edition_with_service_pack_1_x86_x64_dvd_x14-40187.iso)
2) Extract the whole dvd to a Folder (D:\MOSS2007)
3) Delete all the content from the Updates Folder (D:\MOSS2007\x64\Updates)
4) Download Windows SharePoint Services 3.0 SP2 and Office SharePoint Server 2007 SP2 to a folder (D:\SharePoint)
5) Go to the command prompt and extract the above two files in the Updates Folder i.e in (D:\MOSS2007\x64\Updates)
   by running the below two commands
6) wssv3sp2-kb953338-x64-fullfile-en-us.exe /extract:[Path to installation bits]\Updates /quiet
   D:\SharePoint\wssv3sp2-kb953338-x64-fullfile-en-us.exe /extract:D:\MOSS2007\x64\Updates /quiet
7) officeserver2007sp2-kb953334-x64-fullfile-en-us.exe /extract:[Path to installation bits]\Updates /quiet
   D:\SharePoint\officeserver2007sp2-kb953334-x64-fullfile-en-us.exe /extract:D:\MOSS2007\x64\Updates /quiet
8 Delete wsssetup.dll file from the Updates Folder
9) If you want you can download any cumulative updates for WSS3.0 and MOSS2007 and extract the  files in the same way to the Updates and Folder and the MOSS installation will apply those updates while installing MOSS2007.
10)Go to the x64 folder and run the setup.exe file.

Thats It!

Thanks,
Sudhir

goes with me, i like to run virtual harddisk in virtualpc. One of my friend gave me a virtual harddisk image that was vmware supported. So i thought instead of downloading and installing and then running the image in a vmware software, is there no way that i can convert this image to virtualpc supportive. After googling for few seconds i found the tool

for doing this and was more happy and satisfied when i found a tool which can resize your existing virtual harddisk space, on the same site.

So the tool names are VMDK(VMWare) to VHD Converter and VHD Resizer

The link to both the tools are http://vmtoolkit.com/files/default.aspx

Thanks,

Sudhir

SO instead of going into depth about telling you about different build automation tool(google it!), i
would directly start with the tool called ‘cruiseControl’ which is a build automation framework
which almost support all the building tool like devenv(visual studio),NANT,msbuild etc.

So this article is all about the combination of cruisecontrol (build autmation framework) ,
Source Vault (Project Repository) and devenv.com (building tool).

Pre Requisite :- download and install latest version of cruise control (mine is v1.4.4)

SOurce vault repository present and Visual studio 2005/2008 installed

All the settings which you would like to make to a file and would like the behavior be as per the
settings described in the one file are done in the ccnet.config. The path to the ccnet.config is
c:\program files\cruisecontrol.NET\server.

In my organization i configured the build server for windows application.
The build server performed some particular task and all the tags for it are in the code below

1)To take the source from the source vault/fortress use vault/fortress client to authenticate and
get the latest code form the source repository
2)Building the latest code using the devenv.com
3)Publishing the latest build on the network drive or on a local drive which is shared
4)Writing the build log for every failure or exception or successful build
5)And then sending the email notification to the admin for every build ,automatically triggered
or forced build and for the developers separately if the build fails by the developer.

Below is the code for the ccnet.config for above tasks

<cruisecontrol xmlns:cb=”urn:ccnet.config.builder”>

<project>

<name>Project1</name>

<triggers>

<intervalTrigger seconds=”1800″/>

</triggers>

<sourcecontrol type=”vault” autoGetSource=”true” applyLabel=”true”>

<executable>C:\Program Files\SourceGear\Fortress Client\vault.exe</executable>

<username>username for source vault/fortress</username>

<password>password for source vault/fortress</password>

<host>Source vault/Fortress Server name</host>

<repository>Root Directory name</repository>

<folder>$/Project1/</folder>

<ssl>false</ssl>

<timeout units=”minutes”>10</timeout>

<useWorkingDirectory>true</useWorkingDirectory>

<workingDirectory>C:\Program Files\CruiseControl.NET\server\Project1\WorkingDirectory</workingDirectory>

{ this is default, you can change it to your desired location}

</sourcecontrol>

<tasks>

<devenv>

<solutionfile>C:\Program Files\CruiseControl.NET\server\RecoveryTrac\WorkingDirectory\Project1.sln</solutionfile>

<configuration>Debug</configuration>

<executable>C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\devenv.com</executable>

<buildTimeoutSeconds>600</buildTimeoutSeconds>

<version>VS2008</version>

</devenv>

</tasks>

<publishers>

<buildpublisher>

<sourceDir>C:\Program Files\CruiseControl.NET\server\Project1\WorkingDirectory</sourceDir>

<publishDir>C:\CruiseBuilds\Project1\test_build</publishDir>

<useLabelSubDirectory>true</useLabelSubDirectory>

<alwaysPublish>false</alwaysPublish>

</buildpublisher>

<xmllogger />

<email mailhost=”SMTP Server name” from=”admin@admin.com” includeDetails=”true”>

<users>

<user group=”buildmaster” address=”admin@admin.com”/>

<user group=”developers” address=”developer1@admin.com”/>

<user group=”developers” address=”developer2@admin.com”/>

</users>

<groups>

<group notification=”change”/>

<group notification=”always”/>

</groups>

</email>

</publishers>

</project>

</cruisecontrol>

Thats It!

More on NANT and msbuild soon…

Thanks

Sudhir