Command line switches of devenv.exe


To see this list, type devenv /? on command prompt

    • /build – build the specified solution configuration
    • /project – specifies the project to build instead of solution, must specify /build to use /project
    • /projectconfig – specifies project configuration to build, must specify /project to use /projectconfig
    • /out – write build output to specified file
    • /rebuild – like /build, but forces a clean first
    • /clean – clean up build outputs
    • /deploy – build the specified solution configuration and then deploy it
    • /run – run the specified solution configuration
    • /runexit – run the specified solution configuration and then terminate
    • /command – executes the specified internal command line after startup
    • /mditabs – use tabbed documents interface
    • /mdi – use MDI interface
    • /fn – use specified font name
    • /fs – use specified font size
    • /LCID – use specified language ID
    • /noVSIP – disables VSIP developers license key for VSIP testing
    • /safemode – only default environment and services load for stability
  • /resetskippkgs – allow VSPackages once flagged for loading failures to load again

Windows XP/2000 Commands & Tools


Windows XP/2000 Commands & Tools

Here’s the ultimate Windows XP/2000 command list that will make any Linux user feel at home at the command prompt. A lot of these commands are intended for administrating a network, but they are great for savvy home users as well.  We even listed which OS you need for these commands. Windows Script and Tricks

Apache Ant, Python Script, Windows Script

Many thanks to the digg users who ‘dugg’ our site and care to leave comments of helpful commands that we have left out!

  • at (windows XP/2000)
    Scheduling utility.
  • bootcfg (XP only)
    This utility allows you to set up your boot options, such as your default OS and other loading options.
  • cacls (XP, 2000, & NT4.0)
    Changes the ACLs (security Settings) of files and folders. Very similar to chmod in Linux. 
  • comp (XP & 2000)
    This utility is very similar to diff in Linux.  Use the /? switch to get examples of command usage.
  • contig (works with NT4.0 and newer)
    A great defrag utility for NTFS partitions.
  • control (XP only) – unpublished!
    Allows you to launch control panel applets from the command line. 
    control userpasswords2, for example will launch a helpful local user admin utility.
  • defrag (XP only – NT4.0 and Win2k use contig)
    Yes, XP comes with a command line disk defrag utility. If you are running Win2k or NT4.0 there is still hope. Contig is a free defrag program that I describe on the defrag page.
  • diskpart (XP only)
    Use this command to manage your disk partitions.  This is the text version for the GUI Disk Manager.
  • driverquery (XP only)
    Produces a list of drivers, their properties, and their versions. Great for computer documentation.
  • eudcedit (XP only) – unpublished!
    Private Character editor.  Yes with this program built into Windows XP you can create your own font!
  • fsutil (XP only) – unpublished!
    This is a utility with a lot of capability.  Come back soon for great examples.
  • getmac (XP & 2000)
    This command gets the Media Access Control (MAC) address of your network cards.
  • gpresult (XP & 2000)
    This generates a summary of the user settings and computer group policy settings.
  • gpupdate (XP only)
    Use this utility to manually apply computer and user policy from your windows 2000 (or newer) domain.
  • ipconfig (XP, 2000 & NT4.0)
    This handy tool displays IP settings of the current computer and much more.
  • MMC (XP, 2000 & NT4.0) – Microsoft Management Console
    This is the master tool for Windows, it is the main interface in which all other tools use starting primarily in Windows 2000 and newer systems.
  • more
    Utility used to display text output one screen at a time. Ex. more c:\windows\win.ini
  • msconfig (XP only)
    The ultimate tool to change the services and utilities that start when your Windows machine boots up. You can also copy the executable from XP and use it in Win2k.
  • msinfo32 (XP &smp; 2000)
    An awesome diagnostic tool. With it you can get a list of running processes, including the residing path of the executable (great for manually removing malware) and get detailed information about hardware and system diagnostics.
  • narrator (XP only)
    Turns on the system narrator (can also be found in accessibility options in control panel).  Will will allow your computer to dictate text to you.
  • netsh (XP & 2000)
    A network configuration tool console.  At the ‘netsh>’ prompt, use the ‘?’ to list the available commands and type “exit” to get back to a command prompt.
  • nslookup (all)
    A DNS name resolution tool.
  • openfiles (XP Only)
    Allows an administrator to display or disconnect open files in XP professional. Type “openfiles /?” for a list of possible parameters.
  • Pathping (XP & 2000)
    A cross between the ping and traceroute utilities. Who needs Neotrace when you can use this? Type “pathping <ip address>” and watch it go.
  • recover (XP & 2000)
    This command can recover readable information from a damaged disk and is very easy to use.
  • reg (XP & 2000)
    A console registry tool, great for scripting Registry edits.
  • sc (XP & 2000)
    A command line utility called the Service Controller.  A power tool to make service changes via a logon/logoff or startup/shutdown script.
  • schtasks (XP only)
    A newer version of the AT command.  This allows an administrator to schedule and manage scheduled tasks on a local and remote machines.
  • secedit (XP & 2000)
    Use this utility to manually apply computer and user policy from your windows 2000 (or newer) domain.  Example to update the machine policy: secedit /refreshpolicy machine_policy /enforce
    To view help on this, just type secedit.
    NOTE: In Windows XP SP1 and news, this command is superceded by: gpupdate /force
  • sfc (XP & 2000)
    The system file checker scans important system files and replaces the ones you (or your applications) hacked beyond repair with the real, official Microsoft versions.
  • shutdown (XP & 2000)
    With this tool, You can shut down or restart your own computer, or an administrator can shut down or restart a remote computer.
  • sigverif (XP only)
    Microsoft has created driver signatures. A signed driver is Microsoft tested and approved. With the sigverif tool you can have all driver files analyzed to verify that they are digitally signed. Just type ‘sigverif’ at the command prompt.
  • systeminfo (XP only)
    Basic system configuration information, such as the system type, the processor type, time zone, virtual memory settings, system uptime, and much more.  This program is great for creating an inventory of computers on your network.
  • sysedit (XP/2000)
    System Configuration File Editor.  An old tool that was very handy for the Windows 9X days.  msconfig is what you want to use now.
  • tasklist (XP pro only)
    Tasklist is the command console equivalent to the task manager in windows. It is a must have when fighting scumware and viruses. Try the command:
    tasklist /svc
    to view the memory resources your services take up.
  • taskkill (XP only)
    Taskkill contains the rest of the task manager functionality.  It allows you to kill those unneeded or locked up applications.
  • tree (XP & 2000)
    An amazing experience everyone should try!  This command will provide a ‘family tree’ style display of the drive/folder you specify.
  • WMIC (XP & 2000)
    Windows Management Instrumentation Command tool.  This allows you to pull an amazing amount of low-level system information from a command line scripting interface.




Step to setting subversion server for administrator:-
1. Check to see if subversion is installed:-
# rpm -q subversion
#svn –version
svn, version 1.5.2 (r32768)
compiled Oct 4 2008, 02:48:59
If you see “package subversion not installed” you will need to install subversion before
proceeding. Otherwise you should see something similar to “ subversion-1.4.4-1.fc7”
2. Login in as root:-
3. Create a directory to hold all your repositories:-
#mkdir /home/svnserver/svn
4. Create a repository. In this example we will create a repository called “repositories”:-
# svnadmin create /home/svnserver/svn
5. list the repository files and directory :-
conf db format hooks locks README.txt
6. Create a SVN user
6.1 vi /home/svnserver/svn/conf/svnserve.conf
In that file add these three lines:
Note:- Do not leave space before this three lines.
6.2 Create a password file.
vi /home/svnserver/svn/conf/passwd
In that file add a line for your user:
# add users in the format : user = password
user = mypassword
7. Create a directory to hold all your project in repositories:-
# mkdir /home/svnserver/svn/myproject
8. Try importing source code into the repository. Change to a directory containing the files you want to
check in.
# svn -m “Intailly importing” import /home/svnproject/source/myproject file:///home/svnserver/svn/myproject
9. Start the SVN Server as Daemon:-
#svnserve -d
10. Try checking it out of the repository:- (Check out)
home/user/source# svn co svn://
11. Try checking it in of the repository:- ( Check in)
#svn ci -m “log message” /home/user/source/myproject/

Release Artificats with Maven Release and Git Flow Plugins


There are various ways using you can release the artifacts.  There are two plugins which is being frequently used is…

  1. Maven Release Plugin
  2. Maven Git Flow Plugin

Maven Release Plugin
This plugin is used to release a project with Maven, saving a lot of repetitive, manual work. Releasing a project is made in two steps: prepare and perform.

Maven Git Flow Plugin
The Maven JGit-Flow Plugin is based on and is a replacement for the maven-release-plugin enabling support for git-flow style releases via maven.


Inrtroduction of Sonatype Nexus


Sonatype Nexus: Manage Artifacts
Sonatype Nexus sets the standard for repository management providing development teams with the ability to proxy remote repositories and share software artifacts. Download Nexus and gain control over open source consumption and internal collaboration.

Why Nexus?

A repository manager stores and organizes binary software components for use in development, deployment, and provisioning. Repository managers serve four primary purposess:

  • Provides a central point for management of binary software components and their dependencies
  • Provides a solid component repository for a complete Component Lifecycle Management approach
  • Acts as highly configurable proxy between your organization and public repositories
  • Provides a deployment destination for internally developed binary components

Repository managers have become essential infrastructure for component-based software development. To the right is a diagram that depicts where a repository manager fits into a typical development process.

The Benefits of a Repository Manager

A repository manager encourages collaboration, speeds build times, and improves visibility and control over component usage. Some of the specific benefits you’ll see from a repository manager include:

  • Faster and more reliable builds

Caching components locally eliminates the need to download dependencies over the Internet, saving time and eliminating the risk that the Internet or remote server won’t be available during the build.

  • Improved collaboration

It provides a mechanism for developers to share binary components for internally developed software projects. The repository manager becomes a deployment target when components are created, and the standard source of both internally developed and open source components for use in development.

  • Component usage visibility

By examining the components present in the repository manager you’ll have visibility into what internally developed components are available and what components developers have downloaded from public repositories.

  • Enforce component standards

Problematic components that don’t meet your standards can be kept out of the repository so developers won’t use them. The challenge is to ensure that all developers and build systems acquire components only from the enterprise repository manager.

  • Controlled sharing with partners

Partner-specific repositories with access controls allow you to choose which components and projects to share.

  • Ideal repo for robust governance

It provides the basis for storing components, which is an integral part of an overall Component Lifecycle Management solution.

Nexus OSS Manual Setup


Step by Step Instruction to Upgrade Perforce to 2014


Step by Step Instruction to Upgrade Perforce to 2014

The step are as follows:

a) Check if the license is current.

p4 license -o

The expiry date must be later than the binary release date you are installing

b) Verify server archives using the command ‘p4 verify -q //… > verify.txt’

* Note – If the file ‘verify.txt’ contains a ‘BAD!’ or MISSING!’
signature during the verify command, please contact Perforce Support prior to upgrading.
** If the depot is large and you get an error message “Request too large for server memory”, you can split the verify to check chink of the depot:

p4 verify -q //depot/project1/… > prj1-verify.txt
p4 verify -q //depot/project2/… > prj2-verify.txt
p4 verify -q //depot/project3/… > prj3-verify.txt

c) Stop the Perforce Server.

p4 admin stop

d) Make a checkpoint of the database.

p4d -r P4ROOT -J journal -jc

e) Copy the db.* files to a safe location.

f) Backup your archive files.

g) Read the release notes so you are aware of the latest changes.

h) Download the latest P4D version.

i) Verify that the newly downloaded binary is the latest. You might need to copy the p4d.exe to p4s.exe

p4d.exe -V
p4s.exe -V

j) Install the upgraded version of the Perforce server.

k) Restore the Perforce Server using the new P4D Binary and the checkpoint taken from the old P4D binary, with the following command ‘p4d –r root –jr’.

l) If the server contains more than 1000 changelists, please run the following command ‘p4d -r root -xu’ from the command line’.

m) Start the perforce Sever.

n) Verify server archive files.

p4 verify -q //… > upgrade-verify.txt

** Note – If the file ‘upgrade-verify.txt’ will contains a ‘BAD!’ or MISSING!’ signature during the verify command, please contact us.

o) Take a checkpoint
p4d -r root -J journal -jc

This is also explained in the below article:

Upgrading to 2013.3 and beyond –

Windows To Linux
Moving from Linux to Windows is not a trivial issue, and such a migration is also not supported and will most likely require consolidation of case sensitivity conflicts using our P4 Migrate product. Please see the link below:

Cross-Server Platform Migration

Change of Server is a “Self-serve” option, please fill out this form and licensing will update accordingly.
P4 Support Change of Server License Request

Please pass the -z switch during the replay as the checkpoint/journal you are replaying are compressed:
p4d -r P4ROOT -jr -z checkpoint.ckp.104.gz

You will need to request for a background user I believe to be able to do all the required command. This can be done by filling in this below form and using one background user for all of you build machines.

Moving a Perforce Server

 By Chris Lesemann <

Our Knowledge Base has accurate and up to date information that will help you prepare your own procedure for upgrading. Because the database structures have changed, you will need to take an existing checkpoint and then replay that checkpoint with the 2014.1 version of the P4 Server.

It appear you are on a 32-bit Windows instance…will you be doing an inplace upgrade or moving to 64-bit hardware? If you are moving from 32-bit to -64bit you have to recover from checkpoint anyway.

Please review the two links below and if you have any further questions I would be happy to assist you:

 Upgrading to 2013.3 and beyond <– specific procedure for moving from 2013.2 and earlier P4 to 2013.3 and later

 Upgrading a Perforce Server <– in-place upgrade

 Moving a Perforce Server <– if you have to move to new hard – do NOT start a 64-bit P4D binary against 32-bit db.* databases, or vice versa.

 Upgrading the Perforce Proxy

General information on the new Btree structures and functionality:

 BTree Format Changed for Perforce Server Versions 2013.3 and Later

 Lockless Reads

Tagged : / / / / / / / / / / / / / / / / /

Introduction of Gradle


Gradle is build automation evolved. Gradle can automate the building, testing, publishing, deployment and more of software packages or other types of projects such as generated static websites, generated documentation or indeed anything else.
Gradle combines the power and flexibility of Ant with the dependency management and conventions of Maven into a more effective way to build. Powered by a Groovy DSL and packed with innovation, Gradle provides a declarative way to describe all kinds of builds through sensible defaults. Gradle is quickly becoming the build system of choice for many open source projects, leading edge enterprises and legacy automation challenges.


We are convinced that Gradle 2.0 is the best available enterprise build system. Yet we are far from done. Learn about upcoming features in Gradle including:

  • Configuration Tasks
  • Persistable Build Configuration
  • Variant Aware Dependency Management
  • Parallel Task Execution
  • Watcher Mode for Daemon
  • Global Cache


Ways to Perforce server Disk Space Cleanup and Repos Size Management



  1. Cleaning up Old Checkpoints
  2. Playing with Symlink(Softlink) and Redirecting the ROOT folder to drive where we have enough place.
  3. Deleting db.have and recreate it manually
  4. Display disk space information on the server using “p4 diskspace”
  5. Display size information for files in the depot using “p4 sizes”
Tagged : / / / / / / / / / / / / / / / / /

Interview Questions and Answer for Perforce Version Control Tool


Some of the perforce commands which is not commonly used but useful.
p4 annotate – Print file lines along with their revisions.
e.g p4 annotate file.c

How to ignore files/folder in perforce workspace/client?
Assuming you have a client named “CLIENT”, a directory named “foo” (located at your project root), and you wish to ignore all .dll files in that directory tree, you can add the following lines to your workspace view to accomplish this:

-//depot/foo/*.dll //CLIENT/foo/*.dll
-//depot/foo/…/*.dll //CLIENT/foo/…/*.dll

The first line removes them from the directory “foo” and the second line removes them from all sub directories. Now, when you ‘Reconcile Offline Work…’, all the .dll files will be moved into “Excluded Files” folders at the bottom of the folder diff display. They will be out of your way, but can still view and manipulate them if you really need to.

You can also do it another way, which will reduce your “Excluded Files” folder to just one, but you won’t be able to manipulate any of the files it contains because the path will be corrupt (but if you just want them out of your way, it doesn’t matter).

-//depot/foo.../*.dll //CLIENT/foo.../*.dll

How can I exclude a directory from a Perforce command?

Specify a file that contains a list of files to ignore when adding files to the depot and reconciling workspaces.

How to check last 10 submitted, pending, or shelved changelists that include any file under the project directory?
p4 changes -m 5 //depot/project/…

How to check last 10 submitted or pending, or shelved changelists that include any file under the project directory?
p4 changes -m 1 -s submitted | pending | shelved

Interview Questions Related to Perforce Admin

  1. How to take perforce backup
  2. How to restore perforce backup
  3. How to verify health of the perforce repos database
  4. What is the ise of p4 dbverify and p4 verify

What is the use of p4 admin commands.

The p4 admin command allows Perforce superusers to perform administrative tasks even when working from a different machine than the one running the shared Perforce service.
p4 [g-opts] admin checkpoint [ -z | -Z ] [ prefix ]
p4 [g-opts] admin journal [ -z ] [ prefix ]
p4 [g-opts] admin stop
p4 [g-opts] admin restart
p4 [g-opts] admin updatespecdepot [ -a | -s type ]
p4 [g-opts] admin resetpassword -a | -u user
Reference – Click here

How to remove files from perforce permanently?
p4 archive -p with caution. This is the one of only two commands in Perforce that actually removes file data. (The other command that removes file data is p4 obliterate.)

How to set properly in Perforce?
The Perforce service offers three ways of storing metadata: counters/keys, attributes, and properties.

If your application requires only the flat storage of simple key/value pairs, and attempts to implement no security model, use the p4 counters and p4 keys commands.

The p4 property command can be used by administrators to view and update property definitions stored in the Perforce service. The service does not use the property definitions; it provides this capability for other Perforce applications, such as P4V

If your application’s metadata is associated with particular files, use p4 attribute.

If your application’s metadata is not associated with files, and if you have a requirement to restrict its visibility to users, groups, and/or to control the precedence of multiple values using sequence numbers, use p4 property.

p4 property -n name -v value
p4 counter mycounter 123
p4 key mykey 12
p4 attribute -n name [ -v value ] files…

Perforce Integration with other Tools

  1. Gitfushion
  2. Swarm
  3. Replication
Tagged : / / / / / / / / / / / / / / /

AnthillPro Training | AnthillPro Course | Online | Classroom | India


Course Summary

AnthillPro automates the process of building code into software projects and testing it to verify that project quality has been maintained. This course will teach students the processes needed for building a project, setting up a Continuous Integration build, deploying artifacts, and integrating third-party tools. The students will learn to identify bugs and errors using AnthillPro to track, collate, and test changes in real time to a collectively maintained body of computer code.

Topics Covered In This Course


  • About AnthillPro
  • Projects
  • Workflows
  • Jobs
  • Build Concepts
  • Dependencies and Artifacts
  • Environments
  • Life-Cycle Models

Getting Started

  • Setting Up a Build Process
  • Setting Up a Continuous Integration Build
  • Setting Up a Deployment Process
  • Integrating Other Tools Into Processes


  • Installing AnthillPro
  • Unattended Agent Installation Scripts
  • Installing Distributed Servers


  • Upgrading AnthillPro
  • Upgrading Distributed Servers
  • What’s New in AnthillPro


  • Setting Up Security
  • Perform Security Audits
  • Securing Artifact Sets
  • Set Up and Manage Guest Users


  • Overview
  • Create Schedules


  • Reporting Basics
  • Complex reports

Dependency Management

  • Overview
  • Configure Dependencies
  • Using Codestation Projects
  • Configure Dependencies Tutorial

Advanced Authoring

  • Managing Projects
  • Managing Workflows
  • Managing Jobs
  • Reusing Workflow Definitions and Jobs
  • Managing Life-Cycle Models
  • Managing Notifications
  • Managing Properties
What You Can Expect

At the end of the course, students will be able to:

  • Understand the installation process
  • To set up AnthillPro
  • Understand how to begin project creation
  • Use customizations
  • Use AnthillPro to perform continuous integration
Training Style

Lecture (50%) / Workshop (50%)

scmGalaxy is a community initiatives based on Software configuration management that helps community members to optimize their software development process, Software Development Life Cycle optimization, Agile Methodologies and improve productivity across all aspects of Java development, including Build Scripts, Testing, Issue Tracking, Continuous Integration, Code Quality and more. scmGalaxy group that helps organisations optimize their software development process. We provide consulting, training and mentoring services in Agile Development Practices such as Version Management, Continuous Integration, Build Management, Test-Driven Development, Acceptance-Test Driven Development, Build Automation, Code Quality Practices and Automated Testing.

We provide job oriented training in the area of Configuration management, Build and Release Engineering. Candidates with engineering or software background and looking to either start or change their career to Build and Release Engineering, would benefit most from this training. Instructor-led training course offered in India, Bangalore, Delhi, Pune, Mumbai and Hydrabad. Instructor is an expert in Software configuration management, Build and release engineering with more than 15 years industry experience in india.The Goal of the course make the training attendants equip with all the concepts of build and release engineering.

Contact us at

Course Objectives
To bring your team up to speed with agile development, We can also run the from Continuous Integration to Continuous Delivery with autoamted course within your premises.

Course Schedule
This course is an intensive 1-day & 2-day workshop with a mixture of teaching and lab exercises. Currently, this course is offered exclusively as an on-site course. Please contact us for more details.

This is a hands-on, practical course designed to teach specialised skills for real-world development situations. It is thus primarily aimed at a SCM Engineer, Build/Release Engineer and developer audience.

The course is modular and flexible – depending on specific student needs and requests. Through our trainings, you benefit from the wide experience and architectural expertise of our team. We bring that experience to you in an highly interactive, intensely hands-on setting.

We assume participants have a reasonable understanding of Development in any language as well as a basic understanding of the Software Development Life Cycle.

Lab Work
All our courses are above all practical in nature. We believe that the best way to learn is by doing. So the course contains approximately 80% lab work.

Learning Resources
Each registrant will receive a copy of the student notes and lab solutions, a certificate of completion, and a CD containing all the tools covered in the course and CD containing all the tools covered in the course.

Contact Us
This course is provided on-site, and can be tailored to your particular requirements. If you would like our trainings delivered at your premises, or for any additional information please contact us. Please email us at | Call – +91 700 483 5930 | Skype – scmGalaxy

Tagged : / / / / / / / / / / / / / / / /