Re: REPOST: Specifying app relative path in debug command line?

Tech-Archive recommends: Speed Up your PC by fixing your registry

Hongye
Thank you for your response. I will try your suggestions to see if it
solves the problem. As for the managed no-spam account I'm not sure what you
are saying. Are you now able to identify my (new) email alias?

I'm having a slightly different problem with a pre build command that I'll
post in a seperate thread -- so I hope my account is now recognized.

Regards,
Bill

""Hongye Sun [MSFT]"" <hongyes@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:ljPn03JmJHA.5168@xxxxxxxxxxxxxxxxxxxxxxxxx
Hi Bill,

Thanks for your post. I am Hongye Sun from Microsoft newsgroup service and
it is my pleasure to work with you on this issue.

Due to a system issue, the renewed managed no-spam account cannot be
identified. That is why we cannot see your original question in newsgroup.
If you have any feedback on this, please do not hesitate to let me know. I
will forward the issue with your comments to the corresponding team. In
the
meanwhile, I will do my best to work with you on this issue to minimize
the
impaction to you.

"Start External Program" and "Command Line Arguments" in Visual Studio
2008
are saved in .user file, which is located at the same folder of the
project
file. It is not recommended to check in .user file in source control,
because it saves user environment specific information. The .user file
will
be excluded by default by most popular source control software, like VSS,
TFS and SVN. It means that you do not need to worry about this issue
because the settings in your machine will not be shared with other
engineers. They must specify them again in their machine.

In addition, if you really need to share the .user file with others,
Visual
Studio supports to specify command line arguments as relative path. Here
are the rules of how Visual Studio finds paths:

1. File paths defined in "Command Line Arguments" are searched under
working folder of current project output folder.

For example: if you only specify "test.dll" without any folder path and
output path is "bin\Debug", NUnit will search for "<Project
Folder>\bin\Debug\test.dll".

For this case, you can type the dll file names in the "Command Line
Arguments" field if the dll files are in the output window.
If you want to find the solution root path, please type "../../../" if the
output path is "bin\Debug".

You can also change the default working folder under the edit box of
"Command Line Arguments".
For detail, please refer to:
http://msdn.microsoft.com/en-us/library/1ktzfy9w.aspx

2. "Start External Program" file is searched at working folder:
"<Disk>:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE", which is
the working folder of Visual Studio process.

For example: if you only specify "NUnit.exe" without any folder path, it
will search "<Disk>:\Program Files\Microsoft Visual Studio
9.0\Common7\IDE\NUnit.exe" file. So in this field, we usually specify
absolute path if the application is not part of Visual Studio.

If other engineers installed NUnit in a different path as yours, there
will
also be a problem.
One workaround is that put NUnit in a share folder and every engineer can
access it. Specify the share folder path in the project properties.

Please note that the best and recommended choice is never to share a .user
file, because it contains many user settings other than Start Options.

Please let me know if you need further information from my side. I will do
my best to follow up.

Have a nice weekend.

Regards,
Hongye Sun (hongyes@xxxxxxxxxxxxxxxxxxxx, remove 'online.')
Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.

Note: MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 2 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions. Issues of this
nature are best handled working with a dedicated Microsoft Support
Engineer
by contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/en-us/subscriptions/aa948874.aspx
==================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.






.

Relevant Pages