Installing Visual Studio 2013 RC SDK generates error - by CoolDadTx

Status : 

  External<br /><br />
		This item may be valid but belongs to an external system out of the direct control of this product team.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 800998 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 9/16/2013 1:42:36 PM
Access Restriction Public

Description

While installing VS 2013 RC SDK on a VS 2013 RC machine I get a popup dialog from VS saying the command line is invalid.

It says this:


Invalid Command Line. Unknown Switch : AllowDuringSetup.

Use:
devenv  [solutionfile | projectfile | anyfile.ext]  [switches]

The first argument for devenv is usually a solution file or project file.
You can also use any other file as the first argument if you want to have the
file open automatically in an editor. When you enter a project file, the IDE
looks for an .sln file with the same base name as the project file in the
parent directory for the project file. If no such .sln file exists, then the
IDE looks for a single .sln file that references the project. If no such single
.sln file exists, then the IDE creates an unsaved solution with a default .sln
file name that has the same base name as the project file.

Command line builds:
devenv solutionfile.sln /build [ solutionconfig ] [ /project projectnameorfile [ /projectconfig name ] ]
Available command line switches:

/Build	Builds the solution or project with the specified solution
	configuration. For example "Debug". If multiple platforms
	are possible, the configuration name must be enclosed in quotes
	and contain platform name. For example: "Debug|Win32".
/Clean	Deletes build outputs.
/Command	Starts the IDE and executes the command.
/Deploy	Builds and then deploys the specified build configuration.
/Edit	Opens the specified files in a running instance of this
	application. If there are no running instances, it will
	start a new instance with a simplified window layout.
/LCID	Sets the default language in the IDE for the UI.
/Log	Logs IDE activity to the specified file for troubleshooting.
/NoVSIP	Disables the VSIP developer's license key for VSIP testing.
/Out	Appends the build log to a specified file.
/Project	Specifies the project to build, clean, or deploy.
	Must be used with /Build, /Rebuild, /Clean, or /Deploy.
/ProjectConfig	Overrides the project configuration specified in the solution
	configuration. For example "Debug". If multiple platforms are
	possible, the configuration name must be enclosed in quotes
	and contain platform name. For example: "Debug|Win32".
	Must be used with /Project.
/Rebuild	Cleans and then builds the solution or project with the
	specified configuration.
/ResetAddin	Removes commands and command UI associated with the specified Add-in.
/ResetSettings	Restores the IDE's default settings, optionally resets to
	the specified VSSettings file.
/ResetSkipPkgs	Clears all SkipLoading tags added to VSPackages.
/Run	Compiles and runs the specified solution.
/RunExit	Compiles and runs the specified solution then closes the IDE.
/SafeMode	Launches the IDE in safe mode loading minimal windows.
/Upgrade	Upgrades the project or the solution and all projects in it.
	A backup of these files will be created as appropriate.  Please
	see Help on 'Visual Studio Conversion Wizard' for more
	information on the backup process.

Product-specific switches:


/componentsDiff Compares two component folders. Requires three arguments:
                OptionalTfsServerCollectionUri SourceVersionedServerFolderPath 
                TargetVersionedServerFolderPath
                If OptionalTfsServerCollectionUri is not provided, then an 
                attempt is made to use the current TFS project collection.

/debugexe	Open the specified executable to be debugged. The remainder of 
	the command line is passed to this executable as its arguments.
/diff	Compares two files.  Takes four parameters:
	SourceFile, TargetFile, SourceDisplayName(optional),
	TargetDisplayName(optional)

/openProjects   Opens versioned project. Requires three arguments:
                OptionalTfsServerCollectionUri VersionedProjectServerItemPath
                OptionalSolutionServerItemPath
                If OptionalTfsServerCollectionUri is not provided, then an 
                attempt is made to use the current TFS project collection.
/TfsLink	Opens Team Explorer and launches a viewer for the 
	provided artifact URI if one is registered.
    /useenv	Use PATH, INCLUDE, LIBPATH, and LIB environment variables
	instead of IDE paths for VC++ builds.

To attach the debugger from the command line, use:
	VsJITDebugger.exe -p <pid>

This occurs while applying "Microsoft Visual Studio 2013 RC Preparation" in the main setup UI.
Sign in to post a comment.
Posted by Microsoft on 9/23/2013 at 3:25 PM
Upgrade to the official RC (http://www.microsoft.com/visualstudio/eng/2013-downloads#d-2013-editions) would solve this problem.
Posted by Microsoft on 9/20/2013 at 3:50 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 9/17/2013 at 12:58 AM
Thanks for reporting the issue. In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided.

It may help if you provide us with:
a setup log file

You can get the log files with the following steps:
1) Download collect.exe from the link below. <http://go.microsoft.com/?LinkId=8967043>
2) You may choose to save the tool for later use, or to run directly.
3) The utility creates a compressed cabinet of all the VS and .NET logs to %TEMP%\vslogs.cab.

You can get more details about how to get the log files here:
http://blogs.msdn.com/heaths/archive/2008/05/09/visual-studio-and-net-log-collection-utility.aspx

Thanks again for your efforts and we look forward to hearing from you.
Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 9/16/2013 at 1:51 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)