Driving me nuts...

  • Thread starter Thread starter Marty
  • Start date Start date
M

Marty

It seems all of the sudden that user controls that
contain images are referencing image sources relative to
the document that I drop the control on. This obviously
does not work beacuase the image source is relative to
the user control, not necessarily the form. Can anyone
tell me why this would be the case?
 
FWIW, this drives me nuts too!

This is how I do it for asp image, after dropping the control on the page
(or user control) I change the ImageUrl to something like
"~/'images/mypicture.jpg"

For an IMG html control I use src="<%=ResolveUrl("~/image/mypicture.jpg")%>"

The drawback to both of these is you don't get to see the actual image in
design mode, only the place marker.

HTH
Brian W
 
Marty,

I'm a bit confused. The URL to the image will have to be relative to the
Webform onto which your user control is placed. If not, the image link
will be broken.

Jim Cheshire [MSFT]
Developer Support
ASP.NET
(e-mail address removed)

This post is provided as-is with no warranties and confers no rights.

--------------------
 
This is exactly the problem

When placing an image control on a UserControl the path assigned to the
image will be relative to the user control which is not necessarily the same
as the webform the user control is placed on.

Take the following example:

I have a folder/structure like this

root \+
Default.aspx
+- images\
mypicture.jpg
+- controls
myheader.ascx
+- help\
about.aspx

if I place an image control on myheader.ascx and use the designer to assign
the image, the designer assigns ../images/mypicture.jpg to the ImageUrl
attribute.

When I place myheader.ascx on Default.aspx (which reside in the root) and
run the app the link to mypicture.jpg is broken because
.../images/mypicture.jpg is not the correct relative path in the context of
Default.aspx.

Now, if I place myheader.ascx on about.aspx (residing in help directory) the
link is un-broken because the relative path for about.aspc is correct.

Clear as mud, right?!?! ;-)

I actually brought this very topic up several months ago in this or the IDE
NG.


Brian W




Jim Cheshire said:
Marty,

I'm a bit confused. The URL to the image will have to be relative to the
Webform onto which your user control is placed. If not, the image link
will be broken.

Jim Cheshire [MSFT]
Developer Support
ASP.NET
(e-mail address removed)

This post is provided as-is with no warranties and confers no rights.

--------------------
Content-Class: urn:content-classes:message
From: "Marty" <[email protected]>
Sender: "Marty" <[email protected]>
Subject: Driving me nuts...
Date: Mon, 10 Nov 2003 11:07:37 -0800
Lines: 6
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Thread-Index: AcOnvefxXWxzEBR1RRmi3tV9aszCgw==
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Newsgroups: microsoft.public.dotnet.framework.aspnet
Path: cpmsftngxa06.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet:189810
NNTP-Posting-Host: TK2MSFTNGXA13 10.40.1.165
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

It seems all of the sudden that user controls that
contain images are referencing image sources relative to
the document that I drop the control on. This obviously
does not work beacuase the image source is relative to
the user control, not necessarily the form. Can anyone
tell me why this would be the case?
Click to expand...
Click to expand...
 
Thanks everyone. I've taken all the feedback and
formulated a few scenarious which now seem to be working
OK.

--------------------------

When using objects that support runat=server, use ~/ to
indicate "virtual root":

<a runat=server href="~/Forms/main.aspx"></a>

When using controls that do not support runat=server
(such as TD to set its background) use Page.ResolveURL:

<TD background="<%=Page.ResolveUrl("~/Images/fadeBG.jpg")
%>" height="5"></TD>

When using javascript for control attributes:

imgHome.Attributes.Add("onMouseOver", "this.src='" &
Page.ResolveUrl("~/Images/btn_home_dn.gif") & "';")
 
Brian,

Let me have a look into this. I'll post back to this thread ASAP.

Jim Cheshire [MSFT]
Developer Support
ASP.NET
(e-mail address removed)

This post is provided as-is with no warranties and confers no rights.

--------------------
From: "Brian W" <brianw@gold_death_2_spam_rush.com>
References: <[email protected]>
Click to expand...
Subject: Re: Driving me nuts...
Date: Mon, 10 Nov 2003 12:15:20 -0800
Lines: 89
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <[email protected]>
Newsgroups: microsoft.public.dotnet.framework.aspnet
NNTP-Posting-Host: dsl-107.goldrush.com 206.171.170.107
Path: cpmsftngxa06.phx.gbl!TK2MSFTNGXA06.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP0
8.phx.gbl!TK2MSFTNGP12.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet:189838
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

This is exactly the problem

When placing an image control on a UserControl the path assigned to the
image will be relative to the user control which is not necessarily the same
as the webform the user control is placed on.

Take the following example:

I have a folder/structure like this

root \+
Default.aspx
+- images\
mypicture.jpg
+- controls
myheader.ascx
+- help\
about.aspx

if I place an image control on myheader.ascx and use the designer to assign
the image, the designer assigns ../images/mypicture.jpg to the ImageUrl
attribute.

When I place myheader.ascx on Default.aspx (which reside in the root) and
run the app the link to mypicture.jpg is broken because
../images/mypicture.jpg is not the correct relative path in the context of
Default.aspx.

Now, if I place myheader.ascx on about.aspx (residing in help directory) the
link is un-broken because the relative path for about.aspc is correct.

Clear as mud, right?!?! ;-)

I actually brought this very topic up several months ago in this or the IDE
NG.


Brian W




Jim Cheshire said:
Marty,

I'm a bit confused. The URL to the image will have to be relative to the
Webform onto which your user control is placed. If not, the image link
will be broken.

Jim Cheshire [MSFT]
Developer Support
ASP.NET
(e-mail address removed)

This post is provided as-is with no warranties and confers no rights.

--------------------
Content-Class: urn:content-classes:message
From: "Marty" <[email protected]>
Sender: "Marty" <[email protected]>
Subject: Driving me nuts...
Date: Mon, 10 Nov 2003 11:07:37 -0800
Lines: 6
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Thread-Index: AcOnvefxXWxzEBR1RRmi3tV9aszCgw==
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Newsgroups: microsoft.public.dotnet.framework.aspnet
Path: cpmsftngxa06.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet:189810
NNTP-Posting-Host: TK2MSFTNGXA13 10.40.1.165
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

It seems all of the sudden that user controls that
contain images are referencing image sources relative to
the document that I drop the control on. This obviously
does not work beacuase the image source is relative to
the user control, not necessarily the form. Can anyone
tell me why this would be the case?
Click to expand...
Click to expand...
Click to expand...
 
For reference, see this thread started December of last year in this very NG

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=OXBB3MEsCHA.1656@TK2MSFTNGP09


Brian W


Jim Cheshire said:
Brian,

Let me have a look into this. I'll post back to this thread ASAP.

Jim Cheshire [MSFT]
Developer Support
ASP.NET
(e-mail address removed)

This post is provided as-is with no warranties and confers no rights.

--------------------
From: "Brian W" <brianw@gold_death_2_spam_rush.com>
References: <[email protected]>
Click to expand...
Subject: Re: Driving me nuts...
Date: Mon, 10 Nov 2003 12:15:20 -0800
Lines: 89
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <[email protected]>
Newsgroups: microsoft.public.dotnet.framework.aspnet
NNTP-Posting-Host: dsl-107.goldrush.com 206.171.170.107
Path:
Click to expand...
cpmsftngxa06.phx.gbl!TK2MSFTNGXA06.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP0
8.phx.gbl!TK2MSFTNGP12.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet:189838
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

This is exactly the problem

When placing an image control on a UserControl the path assigned to the
image will be relative to the user control which is not necessarily the same
as the webform the user control is placed on.

Take the following example:

I have a folder/structure like this

root \+
Default.aspx
+- images\
mypicture.jpg
+- controls
myheader.ascx
+- help\
about.aspx

if I place an image control on myheader.ascx and use the designer to assign
the image, the designer assigns ../images/mypicture.jpg to the ImageUrl
attribute.

When I place myheader.ascx on Default.aspx (which reside in the root) and
run the app the link to mypicture.jpg is broken because
../images/mypicture.jpg is not the correct relative path in the context of
Default.aspx.

Now, if I place myheader.ascx on about.aspx (residing in help directory) the
link is un-broken because the relative path for about.aspc is correct.

Clear as mud, right?!?! ;-)

I actually brought this very topic up several months ago in this or the IDE
NG.


Brian W




Jim Cheshire said:
Marty,

I'm a bit confused. The URL to the image will have to be relative to the
Webform onto which your user control is placed. If not, the image link
will be broken.

Jim Cheshire [MSFT]
Developer Support
ASP.NET
(e-mail address removed)

This post is provided as-is with no warranties and confers no rights.

--------------------
Content-Class: urn:content-classes:message
From: "Marty" <[email protected]>
Sender: "Marty" <[email protected]>
Subject: Driving me nuts...
Date: Mon, 10 Nov 2003 11:07:37 -0800
Lines: 6
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Thread-Index: AcOnvefxXWxzEBR1RRmi3tV9aszCgw==
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Newsgroups: microsoft.public.dotnet.framework.aspnet
Path: cpmsftngxa06.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet:189810
NNTP-Posting-Host: TK2MSFTNGXA13 10.40.1.165
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

It seems all of the sudden that user controls that
contain images are referencing image sources relative to
the document that I drop the control on. This obviously
does not work beacuase the image source is relative to
the user control, not necessarily the form. Can anyone
tell me why this would be the case?
Click to expand...
Click to expand...
Click to expand...
 
I tested this on VS.NET 2002 and the 1.0 and 1.1 Framework and could not
reproduce it. I then tested the same thing on VS.NET 2003 and again could
not reproduce it.

I created a new user control and added an Image control to it. I then set
the image src and it is relative to the user control (which is what I would
expect since the dialog is set to Document Relative.) I then add my user
control to a webform in another folder (so that the relative path will be
different) and then build and browse. The image link is corrected to be
relative to the page.

Can someone encountering this problem provide me with some repro steps?

Jim Cheshire [MSFT]
Developer Support
ASP.NET
(e-mail address removed)

This post is provided as-is with no warranties and confers no rights.

--------------------
From: "Brian W" <brianw@gold_death_2_spam_rush.com>
References: <[email protected]>
Click to expand...
<[email protected]>
Subject: Re: Driving me nuts...
Date: Mon, 10 Nov 2003 15:41:24 -0800
Lines: 142
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <#8XRtQ#[email protected]>
Newsgroups: microsoft.public.dotnet.framework.aspnet
NNTP-Posting-Host: dsl-107.goldrush.com 206.171.170.107
Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet:189892
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

For reference, see this thread started December of last year in this very NG
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=OXBB3MEsCH
Click to expand...
A.1656%40TK2MSFTNGP09


Brian W


Jim Cheshire said:
Brian,

Let me have a look into this. I'll post back to this thread ASAP.

Jim Cheshire [MSFT]
Developer Support
ASP.NET
(e-mail address removed)

This post is provided as-is with no warranties and confers no rights.

--------------------
From: "Brian W" <brianw@gold_death_2_spam_rush.com>
References: <[email protected]>
Click to expand...
Subject: Re: Driving me nuts...
Date: Mon, 10 Nov 2003 12:15:20 -0800
Lines: 89
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <[email protected]>
Newsgroups: microsoft.public.dotnet.framework.aspnet
NNTP-Posting-Host: dsl-107.goldrush.com 206.171.170.107
Path:
Click to expand...
cpmsftngxa06.phx.gbl!TK2MSFTNGXA06.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP 0
8.phx.gbl!TK2MSFTNGP12.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet:189838
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

This is exactly the problem

When placing an image control on a UserControl the path assigned to the
image will be relative to the user control which is not necessarily the same
as the webform the user control is placed on.

Take the following example:

I have a folder/structure like this

root \+
Default.aspx
+- images\
mypicture.jpg
+- controls
myheader.ascx
+- help\
about.aspx

if I place an image control on myheader.ascx and use the designer to assign
the image, the designer assigns ../images/mypicture.jpg to the ImageUrl
attribute.

When I place myheader.ascx on Default.aspx (which reside in the root) and
run the app the link to mypicture.jpg is broken because
../images/mypicture.jpg is not the correct relative path in the context of
Default.aspx.

Now, if I place myheader.ascx on about.aspx (residing in help directory) the
link is un-broken because the relative path for about.aspc is correct.

Clear as mud, right?!?! ;-)

I actually brought this very topic up several months ago in this or the IDE
NG.


Brian W




Marty,

I'm a bit confused. The URL to the image will have to be relative to the
Webform onto which your user control is placed. If not, the image link
will be broken.

Jim Cheshire [MSFT]
Developer Support
ASP.NET
(e-mail address removed)

This post is provided as-is with no warranties and confers no rights.

--------------------
Content-Class: urn:content-classes:message
From: "Marty" <[email protected]>
Sender: "Marty" <[email protected]>
Subject: Driving me nuts...
Date: Mon, 10 Nov 2003 11:07:37 -0800
Lines: 6
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Thread-Index: AcOnvefxXWxzEBR1RRmi3tV9aszCgw==
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Newsgroups: microsoft.public.dotnet.framework.aspnet
Path: cpmsftngxa06.phx.gbl
Xref: cpmsftngxa06.phx.gbl
microsoft.public.dotnet.framework.aspnet:189810
NNTP-Posting-Host: TK2MSFTNGXA13 10.40.1.165
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

It seems all of the sudden that user controls that
contain images are referencing image sources relative to
the document that I drop the control on. This obviously
does not work beacuase the image source is relative to
the user control, not necessarily the form. Can anyone
tell me why this would be the case?
Click to expand...
Click to expand...
Click to expand...
 
Hello Jim,

I've created several user controls with no problem, but
only recently have I included images in them, resulting
in the problem I identified. My app structure is the
following:

<bin>
<images>
<forms>
legal.aspx
...
<usercontrols>
main.aspx

When I place a user control in a same level directory as
the <usercontrols> directory (such as a form in the
<forms> directory all is fine. But when I place a user
control in the main.aspx page, which is in the root, the
images in the user control are not resolved.

This is not really a big deal, but it would sure be nice
to be able to see the images used in the user control in
the designer. As it is now, I had to use the methods I
described in my last post, resulting in empty image
placeholders from the designer. Like I said, it's not a
big deal. Maybe I'm doing something wrong, but I've also
seen other posts from individuals who had to resort to
what I did to make this work. One would think, though,
that the image sources in a user control would correct
themselves when they are placed on a form.
 
Annoying, yes. You didn't reply to the same thread, so I can't see the
previous discussion, but the solution to this problem is to use absolute URL
paths for all your images. For example ...
imgsrc="http://yourdotcom.com/images/myimageisprettierthanyours.jpg"

NOW - I'd love to find a solution to the problem of having multiple projects
.... and having to create multiple copies of the user control so you have one
in each project. Wouldn't it be slick if you could share user controls
across projects without having to create a custom control in a .dll?

mark
 
Mark said:
Annoying, yes. You didn't reply to the same thread, so
Click to expand...

Actually, Marty did reply to the same thread.

previous discussion, but the solution to this problem is to use absolute URL
paths for all your images. For example ...
imgsrc="http://yourdotcom.com/images/myimageisprettierthanyours.jpg"
Click to expand...

Which prevents you from developing on one machine and later copying to a
server (testing or production) with a different path.

In many situations, copying anything to production before it is "released"
is forbidden by policy.

And the solution is as follows:

Use <asp:Image> control and use a relative path (relative to the user
control). For example if your user controls are in a subdirectory called
"Controls" and your images are in "Images" you would do something like the
following:

<asp:image id="img1" runat="server"
imageurl="../images/myimage.jpg"></asp:image>

No matter where the user control is in relation to the document it is placed
on the image will not be broken.

This works with <asp:hyperlink> control too.

This does not work if you use <img> or <a> tags, on your user controls.

If you are using the Property browser use the images selector, make sure
t6he URL Type is set to "Document Relative"


HTH

Regards
Brian W
 
Jim,

Thanks for your time.

I can no longer confirm this on VS.NET 2002. (I don't have it installed any
longer)

I know this behavior is present in VS.NET 2003 present if you are using an
HTML <img> tag, but, that's kind of expected.

I would be interested in performance differences between the 2 following
lines of code:

<img src='<%=ResolveUrl("~/images/mypicture.jpg")%>'

<asp:image id="img1" runat="server"
imageurl="~/images/mypicture.jpg"></asp:image>


Regards
Brian W

Jim Cheshire said:
I tested this on VS.NET 2002 and the 1.0 and 1.1 Framework and could not
reproduce it. I then tested the same thing on VS.NET 2003 and again could
not reproduce it.

I created a new user control and added an Image control to it. I then set
the image src and it is relative to the user control (which is what I would
expect since the dialog is set to Document Relative.) I then add my user
control to a webform in another folder (so that the relative path will be
different) and then build and browse. The image link is corrected to be
relative to the page.

Can someone encountering this problem provide me with some repro steps?

Jim Cheshire [MSFT]
Developer Support
ASP.NET
(e-mail address removed)

This post is provided as-is with no warranties and confers no rights.

--------------------
From: "Brian W" <brianw@gold_death_2_spam_rush.com>
References: <[email protected]>
Click to expand...
<[email protected]>
Subject: Re: Driving me nuts...
Date: Mon, 10 Nov 2003 15:41:24 -0800
Lines: 142
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <#8XRtQ#[email protected]>
Newsgroups: microsoft.public.dotnet.framework.aspnet
NNTP-Posting-Host: dsl-107.goldrush.com 206.171.170.107
Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet:189892
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

For reference, see this thread started December of last year in this very NG
http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&oe=UTF-8&selm=OXBB3MEsCH
A.1656%40TK2MSFTNGP09


Brian W


Jim Cheshire said:
Brian,

Let me have a look into this. I'll post back to this thread ASAP.

Jim Cheshire [MSFT]
Developer Support
ASP.NET
(e-mail address removed)

This post is provided as-is with no warranties and confers no rights.

--------------------
From: "Brian W" <brianw@gold_death_2_spam_rush.com>
References: <[email protected]>
<[email protected]>
Subject: Re: Driving me nuts...
Date: Mon, 10 Nov 2003 12:15:20 -0800
Lines: 89
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <[email protected]>
Newsgroups: microsoft.public.dotnet.framework.aspnet
NNTP-Posting-Host: dsl-107.goldrush.com 206.171.170.107
Path:
Click to expand...
cpmsftngxa06.phx.gbl!TK2MSFTNGXA06.phx.gbl!TK2MSFTNGXA05.phx.gbl!TK2MSFTNGP
0
8.phx.gbl!TK2MSFTNGP12.phx.gbl
Xref: cpmsftngxa06.phx.gbl microsoft.public.dotnet.framework.aspnet:189838
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

This is exactly the problem

When placing an image control on a UserControl the path assigned to the
image will be relative to the user control which is not necessarily the
same
as the webform the user control is placed on.

Take the following example:

I have a folder/structure like this

root \+
Default.aspx
+- images\
mypicture.jpg
+- controls
myheader.ascx
+- help\
about.aspx

if I place an image control on myheader.ascx and use the designer to assign
the image, the designer assigns ../images/mypicture.jpg to the ImageUrl
attribute.

When I place myheader.ascx on Default.aspx (which reside in the root) and
run the app the link to mypicture.jpg is broken because
../images/mypicture.jpg is not the correct relative path in the
Click to expand...
context
of
Default.aspx.

Now, if I place myheader.ascx on about.aspx (residing in help directory)
the
link is un-broken because the relative path for about.aspc is correct.

Clear as mud, right?!?! ;-)

I actually brought this very topic up several months ago in this or
Click to expand...
the
IDE
NG.


Brian W




Marty,

I'm a bit confused. The URL to the image will have to be relative
Click to expand...
to
the
Webform onto which your user control is placed. If not, the image link
will be broken.

Jim Cheshire [MSFT]
Developer Support
ASP.NET
(e-mail address removed)

This post is provided as-is with no warranties and confers no rights.

--------------------
Content-Class: urn:content-classes:message
From: "Marty" <[email protected]>
Sender: "Marty" <[email protected]>
Subject: Driving me nuts...
Date: Mon, 10 Nov 2003 11:07:37 -0800
Lines: 6
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Thread-Index: AcOnvefxXWxzEBR1RRmi3tV9aszCgw==
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
Newsgroups: microsoft.public.dotnet.framework.aspnet
Path: cpmsftngxa06.phx.gbl
Xref: cpmsftngxa06.phx.gbl
microsoft.public.dotnet.framework.aspnet:189810
NNTP-Posting-Host: TK2MSFTNGXA13 10.40.1.165
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

It seems all of the sudden that user controls that
contain images are referencing image sources relative to
the document that I drop the control on. This obviously
does not work beacuase the image source is relative to
the user control, not necessarily the form. Can anyone
tell me why this would be the case?
Click to expand...
Click to expand...
Click to expand...
 
I hear you Mark.

All I can say is that I have confidense in Microsoft, in
that some of these issues might be resolved in a future
release of dotnet. What troubles me, and this might be
better suited for a different thread, is that we have to
firstly experience all of these quirks (however much time
this takes), and then find a 'work-around' for each. I
guess this is inherent with any application. For
instance, when will the day come when we can load VS.Net,
and maybe ComponentOne components, and call it a day?
We're almost there with VS, but I still use Dreamweaver,
Photoshop, and good 'ol TextPad to drill down to levels
that VS isn't so good with. Like I said...I have
confidense in Microsoft.
 
Back
Top