S
Steve
When I create a new project in 2005, and I go to save the project files,
vb.net displays a dialog box that repeats the name of the application and
has a checkbox if I want to create a new directory for it. If I click the
checkbox, the new subdirectory gets the same name as the higher subdirectory
(which is the application name). For example if the project is called Test,
then the subdirectory structure looks like
Visual Studio 2005
--- Projects
--- Test
--- Test
--- bin
--- My Project
--- obj
If I don't tell the dialog to create a new directory, then I get
Visual Studio 2005
--- Projects
--- Test
--- bin
--- My Project
--- obj
Creating another \Test subdirectory below the first \Test subdirectory seems
redundant. Is there a reason why either approach would be better?
Also - If I want to throw in other files into the appliation (such as word
templates, icons, etc.), where's the best place to save them to simplify
deployment and use (\Test, \Test\MyProject, \Test\Test,
\Test\Test\MyProject, somewhere else?
Thanks
Steve
vb.net displays a dialog box that repeats the name of the application and
has a checkbox if I want to create a new directory for it. If I click the
checkbox, the new subdirectory gets the same name as the higher subdirectory
(which is the application name). For example if the project is called Test,
then the subdirectory structure looks like
Visual Studio 2005
--- Projects
--- Test
--- Test
--- bin
--- My Project
--- obj
If I don't tell the dialog to create a new directory, then I get
Visual Studio 2005
--- Projects
--- Test
--- bin
--- My Project
--- obj
Creating another \Test subdirectory below the first \Test subdirectory seems
redundant. Is there a reason why either approach would be better?
Also - If I want to throw in other files into the appliation (such as word
templates, icons, etc.), where's the best place to save them to simplify
deployment and use (\Test, \Test\MyProject, \Test\Test,
\Test\Test\MyProject, somewhere else?
Thanks
Steve