Bugs

[Ayende Rahien]

Recently I've encountered two highly annoying bugs in the framework,
anyone who knows how to solve them would be most appriciated.

1) I'm trying to do Process.Start(u rl); and get a Win32Exception, after
quite a bit of testing I found out that the reason for this is that I
didn't have STAThread attribute. Process.Start(u rl) throws when I don't
have an attribute at all, or when I have MTAThrea, anyone can tell me
why?
I looked around, and it seemed that many other people have encountered
this problem. I've the workaround, but I want to know what is going on
here!

2) The following code throw an exception and abort the program, it
shouldn't!

public static void SetExceptionHan dlers()
{
System.AppDomai n.CurrentDomain .UnhandledExcep tion+=new
UnhandledExcept ionEventHandler (CurrentDomain_ UnhandledExcept ion);
System.Windows. Forms.Applicati on.ThreadExcept ion+=new
System.Threadin g.ThreadExcepti onEventHandler
(Application_Th readException);
}

public static void HandleException (Exception ex)
{
if(ex==null)
return;
using(DetailedE rrorInfo dei = new DetailedErrorIn fo(ex))
{
dei.ShowDialog( );
}
}

private static void CurrentDomain_U nhandledExcepti on(object sender,
UnhandledExcept ionEventArgs e)
{
HandleException (e.ExceptionObj ect as Exception);
}

private static void Application_Thr eadException(ob ject sender,
System.Threadin g.ThreadExcepti onEventArgs e)
{
HandleException (e.Exception);
}
[ STAThread()]
public static void Main(string [] args)
{
SetExceptionHan dlers();
Test();
Console.WriteLi ne("Test passeed");

private void Test()
{
throw new InvalidOperatio nException("Tes t");
}

There is nothing wrong here as far as I can tell, but it still will give
me the silly default dialog. The whole point is to have a better dialog
there!

3) Not related to bugs, but does anyone knows whatever there is a way to
know at *runtime* whatever this is a debug or release build?

[Jochen Kalmbach]

Ayende Rahien wrote:

3) Not related to bugs, but does anyone knows whatever there is a way
to know at *runtime* whatever this is a debug or release build?

The main problem that you first have to define: What is the different
between release and debug build?

From the CLR-View the only difference is the
"System.Diagnos tics.Debuggable Attribute"-Attribute.

This attribute has two properties:
- IsJITTrackingEn abled
- IsJITOptimizerD isabled

If both are "false", then you have a release build.

See:
http://msdn.microsoft.com/library/en-
us/cpref/html/frlrfsystemdiag nostics
debuggableattri buteclasstopic. asp
An other difference might be the generation of PDB-Files. But the
current VS2002/2003 only support the generation of PDB-files with boths
attribut-members set to "true".

If you compile via command-line you can build a release version (no
DebuggableAttri bute-Attribute or both set to false) AND have a PDB-file
generated.
--
Greetings
Jochen

Do you need a memory-leak finder ?
http://www.codeproject.com/tools/leakfinder.asp

Do you need daily reports from your server?
http://sourceforge.net/projects/srvreport/

[Jochen Kalmbach]

Ayende Rahien wrote:

3) Not related to bugs, but does anyone knows whatever there is a way
to know at *runtime* whatever this is a debug or release build?

The main problem that you first have to define: What is the different
between release and debug build?

From the CLR-View the only difference is the
"System.Diagnos tics.Debuggable Attribute"-Attribute.

This attribute has two properties:
- IsJITTrackingEn abled
- IsJITOptimizerD isabled

If both are "false", then you have a release build.

See:
http://msdn.microsoft.com/library/en-
us/cpref/html/frlrfsystemdiag nostics
debuggableattri buteclasstopic. asp
An other difference might be the generation of PDB-Files. But the
current VS2002/2003 only support the generation of PDB-files with boths
attribut-members set to "true".

If you compile via command-line you can build a release version (no
DebuggableAttri bute-Attribute or both set to false) AND have a PDB-file
generated.
--
Greetings
Jochen

Do you need a memory-leak finder ?
http://www.codeproject.com/tools/leakfinder.asp

Do you need daily reports from your server?
http://sourceforge.net/projects/srvreport/

[Jochen Kalmbach]

Ayende Rahien wrote:

1) I'm trying to do Process.Start(u rl); and get a Win32Exception, after
quite a bit of testing I found out that the reason for this is that I
didn't have STAThread attribute. Process.Start(u rl) throws when I don't
have an attribute at all, or when I have MTAThrea, anyone can tell me
why?

Can you please provide a working example !?
Are you using "UseShellExecut e" or normal start with "CreateProc ess" !?

--
Greetings
Jochen

Do you need a memory-leak finder ?
http://www.codeproject.com/tools/leakfinder.asp

Do you need daily reports from your server?
http://sourceforge.net/projects/srvreport/

[Jochen Kalmbach]

Ayende Rahien wrote:

1) I'm trying to do Process.Start(u rl); and get a Win32Exception, after
quite a bit of testing I found out that the reason for this is that I
didn't have STAThread attribute. Process.Start(u rl) throws when I don't
have an attribute at all, or when I have MTAThrea, anyone can tell me
why?

Can you please provide a working example !?
Are you using "UseShellExecut e" or normal start with "CreateProc ess" !?

--
Greetings
Jochen

Do you need a memory-leak finder ?
http://www.codeproject.com/tools/leakfinder.asp

Do you need daily reports from your server?
http://sourceforge.net/projects/srvreport/

[Ayende Rahien]

"Jochen Kalmbach" <no************ ********@holzma .de> wrote in message
news:Xn******** *************** ***********@207 .46.248.16...

Ayende Rahien wrote:

1) I'm trying to do Process.Start(u rl); and get a Win32Exception, after
quite a bit of testing I found out that the reason for this is that I
didn't have STAThread attribute. Process.Start(u rl) throws when I don't
have an attribute at all, or when I have MTAThrea, anyone can tell me
why?

Can you please provide a working example !?
Are you using "UseShellExecut e" or normal start with "CreateProc ess" !?

This is the full source code that cause the problem:

public class Test
{
[System.MTAThrea d()]//NOTICE this, without this, everything works.
public static void Main(string []args)
{
System.Diagnost ics.Process.Sta rt("http://www.google.com" );
}
}

Cause Win32Exception with "The requested section was not present in the
activation context"
I can't repreduce the problem of no *Thread attribute in a simple example
(complex stuff about threading and winforms.

[Ayende Rahien]

"Jochen Kalmbach" <no************ ********@holzma .de> wrote in message
news:Xn******** *************** ***********@207 .46.248.16...

Ayende Rahien wrote:

1) I'm trying to do Process.Start(u rl); and get a Win32Exception, after
quite a bit of testing I found out that the reason for this is that I
didn't have STAThread attribute. Process.Start(u rl) throws when I don't
have an attribute at all, or when I have MTAThrea, anyone can tell me
why?

Can you please provide a working example !?
Are you using "UseShellExecut e" or normal start with "CreateProc ess" !?

This is the full source code that cause the problem:

public class Test
{
[System.MTAThrea d()]//NOTICE this, without this, everything works.
public static void Main(string []args)
{
System.Diagnost ics.Process.Sta rt("http://www.google.com" );
}
}

Cause Win32Exception with "The requested section was not present in the
activation context"
I can't repreduce the problem of no *Thread attribute in a simple example
(complex stuff about threading and winforms.

[Willy Denoyette [MVP]]

The ThreadAttribute can't be the problem source.

Willy.
"Ayende Rahien" <Ay****@no.spam > wrote in message
news:er******** ******@tk2msftn gp13.phx.gbl...

"Jochen Kalmbach" <no************ ********@holzma .de> wrote in message
news:Xn******** *************** ***********@207 .46.248.16...

Ayende Rahien wrote:

> 1) I'm trying to do Process.Start(u rl); and get a Win32Exception, after
> quite a bit of testing I found out that the reason for this is that I
> didn't have STAThread attribute. Process.Start(u rl) throws when I don't
> have an attribute at all, or when I have MTAThrea, anyone can tell me
> why?

Can you please provide a working example !?
Are you using "UseShellExecut e" or normal start with "CreateProc ess" !?

This is the full source code that cause the problem:

public class Test
{
[System.MTAThrea d()]//NOTICE this, without this, everything works.
public static void Main(string []args)
{
System.Diagnost ics.Process.Sta rt("http://www.google.com" );
}
}

Cause Win32Exception with "The requested section was not present in the
activation context"
I can't repreduce the problem of no *Thread attribute in a simple example
(complex stuff about threading and winforms.

[Willy Denoyette [MVP]]

The ThreadAttribute can't be the problem source.

Willy.
"Ayende Rahien" <Ay****@no.spam > wrote in message
news:er******** ******@tk2msftn gp13.phx.gbl...

"Jochen Kalmbach" <no************ ********@holzma .de> wrote in message
news:Xn******** *************** ***********@207 .46.248.16...

Ayende Rahien wrote:

> 1) I'm trying to do Process.Start(u rl); and get a Win32Exception, after
> quite a bit of testing I found out that the reason for this is that I
> didn't have STAThread attribute. Process.Start(u rl) throws when I don't
> have an attribute at all, or when I have MTAThrea, anyone can tell me
> why?

Can you please provide a working example !?
Are you using "UseShellExecut e" or normal start with "CreateProc ess" !?

This is the full source code that cause the problem:

public class Test
{
[System.MTAThrea d()]//NOTICE this, without this, everything works.
public static void Main(string []args)
{
System.Diagnost ics.Process.Sta rt("http://www.google.com" );
}
}

Cause Win32Exception with "The requested section was not present in the
activation context"
I can't repreduce the problem of no *Thread attribute in a simple example
(complex stuff about threading and winforms.

[Ayende Rahien]

"Willy Denoyette [MVP]" <wi************ *@pandora.be> wrote in message
news:e4******** ******@TK2MSFTN GP10.phx.gbl...

The ThreadAttribute can't be the problem source.

Test it, then.
Using MTAThread - exception
Using STAThread - working
Not using at all - works (but I'd some problems with that)