Home Dashboard Directory Help
Search

Félix Perreault by perreault.felix


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


1
0
Sign in
to vote
Type: Bug
ID: 780145
Opened: 2/27/2013 12:23:01 PM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

In a web project, when editing a *.cshtml file, and then start debugging, the Internet browser opens the project to the correct directory (which is ok). The problem is that this page is never correctly interpreted by the browser, and the user has to delete a part of the url to get back to localhost:XXXX/ only, and then navigate back to the edited page. The page should load correctly in the first place. You can actually turn this around by only saving the file in the visual studio editor and only refreshing the page in the browser, but still.
Details
Sign in to post a comment.
Posted by Microsoft on 3/7/2013 at 3:32 AM
Hi, given that we have not heard back from you in 7 days. We will go ahead and close this Connect Issue. If you get a chance to review and provide the information requested earlier, you can go ahead and reactivate this issue.
Posted by Microsoft on 3/4/2013 at 3:20 AM
Hello,

Sorry for bothering. Is there any update?

It would be greatly appreciated if you could provide us with that information as quickly as possible.

Thank you!
Posted by Microsoft on 2/27/2013 at 11:11 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?

Please submit this information to us within 4 business days. We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 2/27/2013 at 12:50 PM
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.