QUOTE(Martyr2 @ 31 Dec, 2007 - 09:39 PM)
Are you attempting to have multiple projects in the same solution? Is the code you are attempting to build trying to reference another project that is not included in the solution?
No, I am only trying to figure out what is broken in one project by comparing it to one that works.
QUOTE(jayman9 @ 31 Dec, 2007 - 11:53 PM)
You need to set the Output path for your project. To access this setting go to the Project menu and select the item at the bottom that starts with the name of the project and ends with Properties. yourProjectName Properties
Select the "Build" tab in the properties tab. Towards the bottom you will see Output Path, you can either browse to to where the files will be stored or just type in a path.
It should be bin\Release\. See screenshot.
Wow! That worked! It was
bin\Debug\ but when I changed it to
bin\Release\ that eror disappeared. Now I have some more common build errors that I think I can deal with.
I do have a question tho'
The sample code I am looking at is supposed
to be a console app. And yet it has the
same sort of structure that a windows app
would have.
Since I am unable to build the app yet, I
am unsure if it is a true console app.
Can a console app have this sort of main
procedure structure?
CODE
using System;
using System.Collections.Generic;
using System.Windows.Forms;
namespace SomeProductNameSample
{
static class Program
{
/// <summary>
/// The main entry point for the application.
/// </summary>
[STAThread]
static void Main()
{
Application.EnableVisualStyles();
Application.SetCompatibleTextRenderingDefault(false);
Application.Run(new MainForm());
}
}
}
| 