Similar Threads:
1.Debug/Start Without Debugging gives IE8 opened with the address bar containing about:blank
I think this is a weid one.
When I do Debug/Start Without Debugging
I get IE8 opened with the address bar containing: about:blank
and the big pane blank.
I close IE that and a new IE opens with the usuall localhost address and a
correct big pane display.
Can you tell me how to avoid that first IE or why I'm getting it?
Thanks
2.Debugged app does not always start
Hi,
I have a very strange problem. I am running VS 2002 on XP Pro.
I have a solution containing several projects.
When I want to debug my application it doesn't always start. Looking at the
output windows, the .NET assemblies get loaded, but when it gets to one of
my assemblies, it hangs. I have to stop debugging, then try again. Sometimes
I have to start my program 20 times before it is launched, other times it
only takes 1-2 attempts.
VS does not crash.
My assemblies do not use a strong key.
Any hints would be apreciated.
Chris
3.VS 2005 always starts Firefox when debugging, not IE
During installation of VS2005 Firefox was my default browser. I changed it
back to IE6 but VS2005 sticks to Firefox when debugging a web site in
development, whatever I try. How to convince VS2005 to use IE ? If at all, I
would expect this behaviour the other way around.
--
Rumoldus,
The Netherlands
4.Starting debug always builds all projects of solution
Solution probably has about 10 projects in it now. I recall as I started
this, it would only build projects with updated sources when running
with debug. Now it builds all projects, even if no sources have changed.
Did I accidentally bump a setting, or something?
5.Process.Start failes on Win 2000 after showing open file dialog
Hi,
I have an application that is launching a process (see the code below) to
perfom some operation on a file. On Windows 2000, if my application first
uses the OpenFileDialog to open a file on the desktop, Process.Start failes
with the following exception:
System.ComponentModel.Win32Exception: The system cannot find the file
specified
at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo
startInfo)
at System.Diagnostics.Process.Start()
at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
The code is roughly as follows:
// here we ask the user to open a file
OpenFileDialog openFileBox = new OpenFileDialog();
openFileBox.Filter = mAddFileFilter.ToString();
openFileBox.FilterIndex = 1;
if(openFileBox.ShowDialog() == DialogResult.OK) {
inputFilePath = openFileBox.FileNames;
}
// later we launch a process to perform an operation on the file
outputFilePath = System.IO.Path.GetTempFileName();
string arguments = "\"" + inputFilePath + "\" \"" + outputFilePath + "\"";
arguments += " /a";
arguments += " /dm1";
arguments += " /DL0";
arguments += " /a1";
arguments += " /h" + progressWindow.ClassId;
string ConverterPath = @"C:\Program Files\foo\bar\converter\go.exe"; // for
example
ProcessStartInfo psInfo = new ProcessStartInfo(ConverterPath, arguments);
psInfo.WindowStyle = ProcessWindowStyle.Hidden;
mProcess = Process.Start(psInfo);
The exception is observed on Windows 2000, but never on Windows XP. It works
fine on Windows 2000 if I never call the OpenFileDialog. I tried setting the
WorkingDirectory of the ProcessStartInfo instance to the directory that
contains the process executable, but this does not help.
Thanks,
Bret
6. Process.Start failes on Win 2000 after showing open file dialo
7. how to tell editor to use same .Net editor already opened
8. System tray icon does not always show when starting app when Windows starts