--> I'm sorry I think I've posted this into the wrong forum before.
I was previously working with Visual Studio 2005 beta 2
and since .NET Framework 2.0 I switched to
Visual Basic 2005 Express Edition.
There is no
"Advanced Compile Options" in the "My Project"/Compile tab.
Is this normal
(I can't set any "optimize" settings)
And for some reason the console window doesn't show up when it's called:
Sub something
Console.Write("something")
End Sub
and when i try this:
Console.Title = "something"
I get this error:
"IO Exception was unhandled"
"The handle is invalid."
I'm bit lost, that never happend before (with VS 2005 beta 2)
Can anyone help me please

"Advanced Compile Options" and Problem with "console"
Brad Eck
<RemoveIntegerChecks>true</RemoveIntegerChecks>
in the containers
<PropertyGroup Condition...Release...">
<PropertyGroup Condition...Debug...">
I think you'll get the idea by just reading the XML. You have to do this with every project where integer overflows can occur.
Hope this (still) helps!
Gravedigger
1) advanced compile options in express
What is the option "remove integer overflow checks" set to in Express
I wished the advanced options had stayed
jesuitx
Here are some thoughts on each of your points:
1) advanced compile options in express
The capability to do this advanced configuration was disabled in Express. Express has a narrower set of features not intended for true professional development and customization.
Express will however enable optimizations by default.
2) writing to the console window
This will work in a Console Application project type. You see your output in the console window.
If you are working in an other project type, like a Windows Application, this Console.Writeline output will only show up in the Output window (Debug->Windows->Output). I suggest you use the Debug.Print("your string") command for common debug traces. You can always see this info in the Immediate Window.
3) setting Console.Title
This only works in Console Application project types. Windows App projects will throw the invalid handle exception. VB Express should have a better error message in this case. If you would like, you can file a bug on http://msdn.com/productfeedback/
Thanks,
Paul