Visual Annotate render problem.

Hi all,

I know this might be a novice question... but hope someone can educate me regarding this issue:

OK 1st let me describe my background abit, we are using ASP.Net work on Windows 2003 IIS as our mdium to host the content.

how we refer our image file and user control is using relative url, example if we have a folder to host the content called "contents" and another to host the image files called "pictures" and both of them are one level under the application root directory


+wwroot (folder)
 +myweb (folder)
  +contents (folder)
   +category (folder)
    -index.aspx
  +pictures (folder)
   +category (folder)
    -header.jpg

so in my presentation template, I code the picture reference url as following:
[html]

[/html]

I didnt use the url mapping done by IWProxy, because for some reason, it cause the .Net application error on TeamSite preview. so I tried the relative path, it works fine, and we decide to go with that.

but when I enable Visual annotate, I found that the review screen do not render the image properly, then I check the source code and found that the Visual Annotate is actually render the page from other folder, which eventually cause the relative path doesn't work. and I provided the image captured during original preview and Visual Annotate preview.

Picture 1: the original preview screen

Picture 2: the visual annotate screen

Can annyone please provide help on this. Thanks in advance

Regards,
waikong

Find more posts tagged with

Comments

gzevin

relative paths are bad, IMO, in general.

You can convert paths to absolute ones, so the issue won't come up

Adam Stoller

relative paths are bad, IMO, in general.

You can convert paths to absolute ones, so the issue won't come up

I'd qualify that by saying '..'-relative paths tend to be bad, doc_root-relative paths tend to be good, and absolute paths are questionable (depending on what you mean by absolute path)

nipper

I'd qualify that by saying '..'-relative paths tend to be bad, doc_root-relative paths tend to be good, and absolute paths are questionable (depending on what you mean by absolute path)

Adam, thanks for making things so confused now.

relative paths (../../images/foo.jpg) are bad, esp with TS templating (& preview). You can do them, but it takes some proxy settings to make it correct.

absolute paths (/images/foo.jpg) are the best

fully qualified paths (http://foo.bar.com/images/foo.jpg) should be avoided at all costs.

gzevin

Adam, thanks for making things so confused now.

relative paths (../../images/foo.jpg) are bad, esp with TS templating (& preview). You can do them, but it takes some proxy settings to make it correct.

absolute paths (/images/foo.jpg) are the best

fully qualified paths (http://foo.bar.com/images/foo.jpg) should be avoided at all costs.

I think that what we mean by 'absolute', Adam thinks it's doc-root relative. Terminology issue, but it looks like we are all on the same ground Smiley Happy

waikong

there was a reason behind that...

once upon a time, I was trying to code the user control in .Net studio, then when i run on TeamSite, I got this error..

Updated on 26-12-2006
I think I know why is the root of the error I am facing, it should because of the .Net DLL file can't recornize the TeamSite path, but when I leave the .Net code using relative path, and image using absolute teamsite path, it works fine.

but do that lead to another problem? which is inconsistant of the code...

please enlighten me