Home Dashboard Directory Help
Search

Visual WD 2013 RC make trouble when I remove the project from list in start page by Anirudha Gupta


Status: 

Closed
 as Won't Fix Help for as Won't Fix


1
0
Sign in
to vote
Type: Bug
ID: 804009
Opened: 9/30/2013 7:36:39 PM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

I moved to bottom of start page. it's should behave as 2012 version
Details
Sign in to post a comment.
Posted by Microsoft on 10/9/2013 at 10:22 AM
Hi Anirudha,

Thank you for your feedback. We have reproduced the issue however we will not be fixing this for Visual Studio 2013. We will address in a future version of Visual Studio.

Tony Goodhew,
Program Manager, VS Pro
Posted by Microsoft on 10/9/2013 at 5:39 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Anirudha Gupta on 10/2/2013 at 8:22 PM
Hello,

follow this step :-

1. Release Visual web developer 13 RC and now make few project. Make more project untill full list of start-page are full in left side from project.

now come to bottom of page( start page) now remove one. now you have moved to top of the page.

now when you remove one more and more then you will be moved to top of pages.

it should be not moving to top when I remove a project from left side list.
Posted by Microsoft on 10/1/2013 at 1:06 AM
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 repro steps to demonstrate this issue so that we can conduct further research?

We look forward to hearing from you with this information.
Posted by Microsoft on 10/1/2013 at 1:04 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.