Somewhere in your definition it's trying to access drive M:, which from the
sound of it is not even defined to your web server.  So, that's two strikes
against it.  Even though you are "running" the web page on your laptop, the
control is still being referenced from the server's perspective.

It sounds to me as though you are building it by referencing the control on
drive M: and that reference is getting saved.  So, when your page gets
rendered it is looking for it in the same location that you are building it
from.  I'm guessing that there is a reference in your project to load the
control from drive M: which is what is causing the issue.

Unfortunately, I'm not a web guy so I can't rattle off the exact location to
look for the reference.  I'd start by looking through your project to see if
you see that drive reference anywhere and change it to a relative path
reference based off the directory on the web server where the project it
deployed to.

...Glenn

On Thu, Oct 9, 2008 at 7:12 PM, Zac <[EMAIL PROTECTED]> wrote:

>
> Hi Glen, thanks! The files for the website are on the same box as IIS
> so that shouldn't be an issue there. Still, that's good to know for
> future reference. M is mapped to the website share on that server from
> my laptop, which is how I'm opening the site through Visual Web Dev.
> Would referencing the compiled Dll locally for the custom control take
> care of this issue?
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web 
Services,.NET Remoting" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/DotNetDevelopment

You may subscribe to group Feeds using a RSS Feed Reader to stay upto date 
using following url  

<a href="http://feeds.feedburner.com/DotNetDevelopment";> 
http://feeds.feedburner.com/DotNetDevelopment</a>
-~----------~----~----~----~------~----~------~--~---

Reply via email to