I've just started using VB.NET, so the following two questions are probably
going to seem ludicrous, but...
1). When some items are added to a project, how exactly are they used? For
example, if a folder is added (or a text file), and then a deployment project
created for that project, the folder (or file) does not appear to be included
in the installation. It just seems to get left behind. I assume that these
items have to be added again to the deployment project.
2). This is related to the above. What is the best way to approach paths in
the development environment to make deployment easier? For example, if I
create an application and use the Directory.GetCu rrentDirectory method, the
result will be the /bin folder in the development environment, which is a
subdirectory of the directory where the previously mentioned items in (1)
above have been stored, whereas when deployed I'm unlikely to want the
executable to be sitting in a subdirectory away from the added items, but
want them to share the same root. I figure there must be a very
straightforward solution to this without having to write code to determine
whether the program is running in the development or deployment environments,
but I can't see what it is.
going to seem ludicrous, but...
1). When some items are added to a project, how exactly are they used? For
example, if a folder is added (or a text file), and then a deployment project
created for that project, the folder (or file) does not appear to be included
in the installation. It just seems to get left behind. I assume that these
items have to be added again to the deployment project.
2). This is related to the above. What is the best way to approach paths in
the development environment to make deployment easier? For example, if I
create an application and use the Directory.GetCu rrentDirectory method, the
result will be the /bin folder in the development environment, which is a
subdirectory of the directory where the previously mentioned items in (1)
above have been stored, whereas when deployed I'm unlikely to want the
executable to be sitting in a subdirectory away from the added items, but
want them to share the same root. I figure there must be a very
straightforward solution to this without having to write code to determine
whether the program is running in the development or deployment environments,
but I can't see what it is.