Changing the Output path

  • Thread starter Thread starter Will Chapman
  • Start date Start date
W

Will Chapman

I have a CF project (C# VS2005) and I want to change
the output folder (i.e. the location where the compiled .EXE
ends up).

I've Saved As and renamed the Solution to another folder but I
still get the .exe being output to the original folder that was chosen
when the project was first created.

Any ideas.......?
 
Tim said:
You can change this setting through the project properties.
Click to expand...
Perhaps I didn't make myself clear. I know I can change the
%CSIDL_PROGRAM_FILES%\C4B setting on the Project
Properties page but what I want to change is the Project Folder.
which can be seen (but is disabled) in the properties box if you
highlight the project in Solution Explorer.

The problem is that this path goes into the Cab.inf file as being the
path to the compiled EXE file....its this path I need to change. I('ve
saved the project to another folder but it keeps the original path for
the compiled Exe.

Thanks for your response...

Will Chapman
--
Cheers.......


Will Chapman
nb Quidditch
 
The Project Folder is where the project file is located. The output is
relative to this location and can be found in the project properties under
the "Build" tab. So if you change to the "Build" tab you'll see the "Output"
at the bottom. By default it should be "bin\Debug\", for the Debug build,
and "bin\Release\" for the Release build. You can change the path there if
you'd rather have the output placed in another location. Is this what you're
looking for or is it still something else that you need?
 
Tim said:
the "Output" at the bottom. By default it should be "bin\Debug\", for
the Debug build, and "bin\Release\" for the Release build. You can
change the path there if you'd rather have the output placed in
another location. Is this what you're looking for or is it still
something else that you need?
Click to expand...
When I create a Cab Project the creation of the .cab file fails (see
earlier thread Makecab/Cab file problems) and I have determined that this is
related to the
paths that are present in the .inf file.

Despite making changes such as the one you have suggested I cannot change
the path of the compiled
..exe file. The most obvious way to do this would be to save the project in
another folder but this is
not permitted as I get an error message "The project file can only be saved
into the project location".

Frustrating!

Cheers

Will Chapman



--
Cheers.......


Will Chapman
nb Quidditch
 
I added a "Smart Device CAB Project" to a solution that contains a smart
device application project. I then set the "primary output" of the
application project to be part of the CAB (right-click the CAB project in
Solution Explorer... Add... Project Output... select the primary output for
the appropriate project). I then built the CAB project and it built
successfully - even though there were spaces in the project folder path.

[SourceDisksNames]
1=,"Common1",,"E:\---- Compact Framework ----\---- 2005 ----\----
CSharp ----\ControlLibrary1\bin\Debug\"
2=,"Common2",,"E:\---- Compact Framework ----\---- 2005 ----\----
CSharp ----\obj\Debug\"

I assume that you created a "Smart Device CAB Project"?
 
Tim said:
I added a "Smart Device CAB Project" to a solution that contains a
smart device application project. I then set the "primary output" of
CSharp ----\obj\Debug\"

I assume that you created a "Smart Device CAB Project"?
Click to expand...
Tim

Yes I have used the Smart Device Cab Project. Its obviously something
peculiar to my (and a number of others judging from threads on various
forums) system. I can only get the Cab to generate if there are no spaces
in the paths. Its a problem that has existed for me since VS2005 Beta and
others have experienced it after upgrading from VS2003 to VS2005.

The only work arounds I've been able to find (other than making sure there
are no spaces in the path) are to use SUBST to convert the paths into
drives,
build the app in non-space-paths or, as I have just discovered, manually
copying project files from the spaced-out-folders to an unspaced-folder.

This has been very time-consuming but I guess I'm now the resident
expert in knowing how to work around the problem! (But a solution
would be better!).

Cheers...

Will Chapman


--
Cheers.......


Will Chapman
nb Quidditch
 
The only other thing that I can think of is to run the VS 2005 pre-RTM clean
tool and reinstall VS 2005 RTM. This would consume even more of your time so
you may just choose to just stick with your workaround. Lots of people have
had various problems with the RTM version of VS 2005 due to the fact that
they had a Beta, or CTP, version installed beforehand.
http://msdn.microsoft.com/vstudio/support/uninstall/default.aspx
 
Back
Top