WinZip Command Line | WinZip Command line CheatSheet – Reference

winzip-command-line

The default action is to add or replace zipfile entries from list, which can include the special name – to compress standard input. If zipfile and list are omitted, zip compresses stdin to stdout.

 -f   freshen: only changed files                   -u   update: only changed or new files

 -d   delete entries in zipfile                         -m   move into zipfile (delete files)

 -k   force MSDOS (8+3) file names           -g   allow growing existing zipfile

 -r   recurse into directories                          -j   junk (don’t record) directory names

 -0   store only                                                   -l   convert LF to CR LF (-ll CR LF to LF)

 -1   compress faster                                       -9   compress better

 -q   quiet operation                                        -v   verbose operation/print version info

 -c   add one-line comments                        -z   add zipfile comment

 -b   use “path” for temp file                        -t   only do files after “mmddyy”

 -@   read names from stdin                        -o   make zipfile as old as latest entry

 -x   exclude the following names              -i   include only the following names

 -F   fix zipfile (-FF try harder)                      -D   do not add directory entries

 -A   adjust self-extracting exe                    -J   junk zip file prefix (unzipsfx)

 -T   test zipfile integrity                                 -X   eXclude eXtra file attributes

 -$   include volume label                              -S   include system and hidden files

 -h   show this help                                          -n   don’t compress these suffixes

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

Command line switches of devenv.exe | Devenv command line switches Guide

devenvexe-command-line-switches

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
Tagged : / / / / / / / / / / / / / / / / / / / /

How to run Remote Desktop Console by using command line?

How to run Remote Desktop Console using command line
If you may want to run Desktop Console from a batch file, for example RDC over VPN, you can use mstsc /v:servername /console command.

Mstsc

Creates connections to terminal servers or other remote computers, edits an existing Remote Desktop Connection (.rdp) configuration file, and migrates legacy connection files that were created with Client Connection Manager to new .rdp connection files.

Syntax

mstsc.exe {ConnectionFile | /v:ServerName[:Port]} [/console] [/f] [/w:Width /h:Height]
mstsc.exe /edit”ConnectionFile”
mstsc.exe /migrate
Parameters

ConnectionFile

Specifies the name of an .rdp file for the connection.
/v:ServerName[:Port]
Specifies the remote computer and, optionally, the port number to which you want to connect.

/console
Connects to the console session of the specified Windows Server 2003 family operating system.

/f
Starts Remote Desktop connection in full-screen mode.

/w:Width /h:Height
Specifies the dimensions of the Remote Desktop screen.

/edit”ConnectionFile”
Opens the specified .rdp file for editing.

/migrate
Migrates legacy connection files that were created with Client Connection Manager to new .rdp connection files.

Remarks
* You must be an administrator on the server to which you are connecting to create a remote console connection.
* default.rdp is stored for each user as a hidden file in My Documents. User created .rdp files are stored by default in My Documents but can be moved anywhere.
Examples

To connect to the console session of a server, type:
mstsc /console

To open a file called filename.rdp for editing, type:
mstsc /edit filename.rdp

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

Command Line to find a Change list properties in perforce server

command-line-to-find-a-change-list-properties-in-perforce-server

Command Line to find a Change list properties and associated path of the file in perforce server view:

Examples of the command you want:
p4 describe 1231928
p4 describe -s 1231928
p4 files @=1231928

Where 1231928 is the change list number.

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

How to Install CollabNet SVN Command Line Client in Solaris?

collabnet-svn-command-line

Link: http://www.collab.net/downloads/subversion/solaris.html

1. Platform and configuration

Product: CollabNet Subversion client

Platforms: Solaris 10 SPARC

Prerequisite: You must be a superuser (root) to install and uninstall

CollabNet Subversion.

2. Import/Update CollabNet certificate

CollabNet Subversion Solaris packages are signed. As a one-time task,

import the CollabNet certificate using the command:

    sudo pkgadm addcert -ty certificate.pem

The CollabNet certificate is available for download at:

http://www.collab.net/nonav/downloads/subversion/certificate/certificate.pem

NOTE: the certificate has changed between 1.5.0 and 1.5.1 release.  The

certificate used for 1.5.0 had a short expiration date so we have created

a new certificate.  If you have previously installed the 1.5.0 certificate,

you must remove it before installing the new one:

    sudo pkgadm removecert “Alexander Thomas(AT)”

Once it is removed you can install the new certificate.

3. First installation

The command to install the CollabNet Subversion client, if a previous version

has not already been installed, is:

    sudo pkgadd -d /path/to/client-sparc-local

4. Updating an existing installation

The proper way to update a Solaris package is to remove the current version

and then install the new version.  If you have the CollabNet Subversion server

installed, you will need to remove it first.  Again, refer to the readme for

that package before proceeding.

    sudo pkgrm CSVNclnt

    sudo pkgadd -d /path/to/client-sparc-local

5. Post-installation instructions

A. CollabNet Subversion installs into /opt/CollabNet_Subversion, which is

   probably not on the executable search path for your system. Add the directory

   /opt/CollabNet_Subversion/bin to your $PATH environment variable. In order to

   make this change affect all users of your system and persists across reboots,

   add the following line to /etc/profile:

    PATH=/opt/CollabNet_Subversion/bin:$PATH

B. CollabNet Subversion provides man pages and localizations for several

   languages. To take advantage of these features, update your MANPATH and/or

   LOCPATH environment variables to include the CollabNet Subversion directories.

   For example:

    export MANPATH=/opt/CollabNet_Subversion/share/man:$MANPATH

    export LOCPATH=/opt/CollabNet_Subversion/share/locale:$LOCPATH

6. Support for CollabNet Subversion

Find out about CollabNet Technical Support at

http://www.collab.net/services/subversion/

Information about CollabNet Training, Consulting, and Migration

services is at http://www.collab.net/services/subversion/training.html

Join openCollabNet for community support: http://open.collab.net

7. About Subversion and CollabNet

CollabNet launched the Subversion project in 2000 in response to the demand

for an open standard for Web-based software configuration management that

could support distributed development. CollabNet continues to be strongly

involved with the Subversion project and offers CollabNet Subversion Support,

Training, and Consulting services.

CollabNet also provides the most widely used collaborative development

environment in the world. More than 1,400,000 developers and IT projects

managers collaborate online through CollabNet. The company is transforming

the way software is developed by enabling organizations to leverage global

development talents to deliver better products and innovate faster.

Visit CollabNet at http://www.collab.net for more information

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