Dreamweaver Namespace issue on my web server

Question

I am hosting my site on GoDaddy.com. I have created a site
using Dreamweaver CS3 and SQL2005. Everything works great on my
local machine, but when I upload it to the remote web server, the
aspx pages do not work. GoDaddy support says it is due to the
second line in every one of my aspx pages, specifically the
namespace attribute. From what I've read, this is automatically put
into every page created by Dreamweaver that contains an asp/asp.net
control. GoDaddy's response is to remove this line from my page and
everything will work great, which obviously it will not. I really
would not like to have to rebuild 32 + aspx pages after already
developing them in Dreamweaver. The actual line they say is causing
the problem is below:
<%@ Register TagPrefix="MM" Namespace="DreamweaverCtrls"
Assembly="DreamweaverCtrls,version=1.0.0.0,publicKeyToken=836f606ede05d46a,culture=neutra l"
%>
Does anyone have any suggestions as to how to get around this
issue?

Answer 1

"carrb69" <[email protected]> wrote in
message
news:[email protected]...
> Joris,
>
> I did have the dll located in a subfolder of the root
directory. I also
> put it
> in the root directory as well after receiving your
previous response and
> got
> the same results. Unfortunately, I would need to go to
GoDaddy to get the
> exact
> error because all I see when I try to access my aspx
pages is a very
> generic
> error. I had to go to GoDaddy previously to figure out
that it was the
> Namespace attribute that was causing the issue. I'll try
this evening to
> get
> them to send me the actual error message and post it
then. Thanks for the
> quick
> responses.
>
> Brian
Hi Brian,
maybe it's your browser that's hiding the error message, if
using MSIE then
please disable the "Show friendly HTTP error messages" option
in Internet
Options.
If that doesn't reveal the error message, try editing the
web.config that
dreamweaver generated for you with the following settings,
(add any missing
settings, and leave the connectionstrings that dreamweaver
has setup intact)
<configuration>
<system.web>
<compilation debug="true"/>
<customErrors mode="Off"/>
<trace
enabled="true"
traceMode="SortByCategory"
requestLimit="10"
pageOutput="false"
localOnly="false"
/>
</system.web>
</configuration>
Debug Compilation should give more insight inrto compilation
errors, which
can allso be done at the page level via<% @ Page
debug=true" %>
Custom Errors Off will disable any error pages that may be
shown in case of
an error, seting it to "emoteOnly" will only thow these page
to external
visitors, but since you are not working on the server that
actually makes
little sense.
The trace setting should enable a HTTP Handler that allows
you to view trace
information from /trace.axd in the root of your website,
enabling pageOutput
will inject the tracing information into every page, which
can allso be done
at the page level via <% @ Page trace=true" %>
There settings do have a performance impact because they are
enabled for
every request in the application, once you've got the errors
out disable
them at the application level and enable them per-page.
Hope this helps
Joris