Search

Problem with NavigateURL of Hyperlink Control by Mike at Visual Consulting

Closed
as Fixed Help for as Fixed

0
0
Sign in
to vote
Type: Bug
ID: 330792
Opened: 2/29/2008 6:01:47 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
This is really a problem with the component responsible for allowing users to pick the property value for the NavigateURL property of the Hyperlink Control.

The problem is pretty simple and if you follow the steps described below you will see it.
Details (expand)
Product Language
English

Version

Visual Studio 2008 (All Products and Editions)
Operating System
Windows XP Professional
Operating System Language
English (US)
Steps to Reproduce
Create a new web site.
Create a new folder called 'affiliate'
In that new folder create a new page called 'Default.aspx'
In that same folder create a new page called 'Signup.aspx'
Go back to the 'affiliate/Default.aspx' page.
Add a Hyperlink control to the page and edit the NavigateURL propery by SELECTING THE ... BUTTON and select the Signup.aspx page in the affiliate subdirectory. The UI will INCORECTLY set the property to 'affiliate/Signup.aspx' instead of 'Signup.aspx'


Actual Results
You end up with the incorrect relative path to the page you are linking to by using the UI.
Expected Results
The relative path should have been just Signup.aspx not affiliate/Signup.aspx
TAP Code (if applicable)
 
      You can indicate your satisfaction with how Microsoft handled this issue by completing this quick 3 question survey. [Details]

 

Sign in to post a comment.
Posted by jnstaub on 4/22/2008 at 12:49 AM
it seems to be the opposite case of my bug ID 338624, if i try to define an image source by the same way , the path is the file name instead of the relativ path images/file.jpg
Posted by Microsoft on 3/2/2008 at 7:17 PM
Thanks for your feedback.

We are escalating 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.

Thank you,
Visual Studio Product Team
Sign in to post a workaround.