Home Dashboard Directory Help
Search

Changed behavior of .NET applications in Windows 8 by coder32-at-live.de


Status: 

Active


1
0
Sign in
to vote
Type: Bug
ID: 785913
Opened: 4/30/2013 6:34:09 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

This text is a translation of a bug report in german (https://connect.microsoft.com/VisualStudio/feedback/details/778081/verhaltens-nderung-von-net-programmen-in-windows-8#details)

Considering a .NET console application (testet with .NET 2.0 and 4.5):

Main () {
(new Form()).ShowDialog(); // blocking statement, program stops (*)

for (i = 0; i < 100000; i++)
    Console.WriteLine(i);
}

(*) If I shut down this program using the new TaskManager in Windows 8 the application will be killed how expected.

Main () {
(new MyForm()).ShowDialog(); // blocking statement, program stops (**)

for (i = 0; i < 100000; i++)
    Console.WriteLine(i);
}

(**) If I close/kill this program like above ShowDialog will be leaved and the following loop will be entered and partially executed. The loop stops sometimes by 1500 iterations or by 3000.
Running Windows 7 this program will be executet how it should be.

The issue I found out is the time defining the Text-property of a Form.
Is the Form.Text-property empty bevor calling Form.ShowDialog() all will be running how it should be. If one set the Form.Text-property (not empty) and then call Form.ShowDialog() the program wont be "killed" normally. The application gets some time for further execution after leaving ShowDialog().
Details
Sign in to post a comment.
Posted by Microsoft on 5/21/2013 at 11:18 AM
Thank you for reporting this issue. Customer feedback is a critical part of a successful, impactful software product. Unfortunately another part is the reality of schedules and the need to prioritize investments according to the objectives of the product. We have evaluated the issue that you have reported and at this point in the product's lifecycle, it does not meet the criteria to be addressed. This evaluation is carefully done and considers many aspects including the cost of the fix, implications of the change, and the number of reported instances of the issue.


Many customers have found it useful to discuss issues like this in the forums (http://social.msdn.microsoft.com/forums/en-US/winforms) where Microsoft and other members of the community can recommend ways of achieving the behavior you are interested in.

Thank you,
The Windows Forms Product Team
Posted by Microsoft on 5/2/2013 at 11:53 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by coder32-at-live.de on 5/1/2013 at 8:53 AM
In additional tests by creating a Windows-Application - instead of creating a console application - I saw the wrong behavior every time. So one can say you will see the right behavior only by creating a console application and setting the "right" Text property.
Posted by coder32-at-live.de on 5/1/2013 at 8:23 AM
I uploaded a test project that can show the issue.

For some more information read my comment inside of the code.
Posted by Microsoft on 4/30/2013 at 10:38 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please give us a demo project to demonstrate this issue so that we can conduct further research?

We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 4/30/2013 at 6:52 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.
File Name Submitted By Submitted On File Size  
killWin8Appl.zip 5/1/2013 9 KB