Difficulty publishing ASP.NET site

I've developed a site using Visual Studio 2005, ASP.NET, C#, and a
MySQL database. I've gotten it debugged under the visual studio
environment, and moved it over to the server on my Domain Controller
(Window 2000 Server, IIS 5.0) and checked it out outside the
development environment.

So I went ahead and got a hosting account (GoDaddy Economy), imported
my MySQL database and checked it out, copied my site using the "Copy
Web Tool" in VS, changed the connection strings in the web.config
file, and tried to fire it up.

The first thing I got was that it couldn't load the MySql connector
assembly that was called for ( Version="5.2.1.0",...>. When I called their tech support the tried to
convince me there was something wrong with my connection string, and
when I insisted that wasn't my problem, the fell back to "We provide
the hosting space. The rest is up to you!" (Oh, well, I guess you get
what you pay for!).

I solved the problem (I think) by including the MySql.Data.dll in the
bin directory. But now it's blowing up with a "Parser Error" on line 1
of the .xsd file for the dataset I'm using. At least line 1 is what's
high-lighted in red on the error page. Line 1 is nothing more than the
XML version definition:"" (The
error was "Failed to generate code. Exception of type
'System.Data.Design.InternalException' was thrown.")


What the heck? I have no idea how to even begin to figure out what has
gone wrong between my environment and theirs that can cause this. Both
my environment and theirs are running .NET Framework 2.0.50727.

Can anyone provide any help? Thanks.

Re: Difficulty publishing ASP.NET site

Did you google it?
Check out folowing links

http://forums.asp.net/p/1011934/1829242.aspx
http://www.velocityreviews.com/forums/t365122-dataset-using- mysql-renders-quotparser-errorquot.html

George


"daveh551" wrote in message
news:7a9a43bb-08d3-49d0-9a1b-e92375f05156@t54g2000hsg.google groups.com...
> I've developed a site using Visual Studio 2005, ASP.NET, C#, and a
> MySQL database. I've gotten it debugged under the visual studio
> environment, and moved it over to the server on my Domain Controller
> (Window 2000 Server, IIS 5.0) and checked it out outside the
> development environment.
>
> So I went ahead and got a hosting account (GoDaddy Economy), imported
> my MySQL database and checked it out, copied my site using the "Copy
> Web Tool" in VS, changed the connection strings in the web.config
> file, and tried to fire it up.
>
> The first thing I got was that it couldn't load the MySql connector
> assembly that was called for ( > Version="5.2.1.0",...>. When I called their tech support the tried to
> convince me there was something wrong with my connection string, and
> when I insisted that wasn't my problem, the fell back to "We provide
> the hosting space. The rest is up to you!" (Oh, well, I guess you get
> what you pay for!).
>
> I solved the problem (I think) by including the MySql.Data.dll in the
> bin directory. But now it's blowing up with a "Parser Error" on line 1
> of the .xsd file for the dataset I'm using. At least line 1 is what's
> high-lighted in red on the error page. Line 1 is nothing more than the
> XML version definition:"" (The
> error was "Failed to generate code. Exception of type
> 'System.Data.Design.InternalException' was thrown.")
>
>
> What the heck? I have no idea how to even begin to figure out what has
> gone wrong between my environment and theirs that can cause this. Both
> my environment and theirs are running .NET Framework 2.0.50727.
>
> Can anyone provide any help? Thanks.

Re: Difficulty publishing ASP.NET site

George,

Thanks so much for your response.

I was so completely baffled by where the error was coming from that I
couldn't imagine what terms to google for.

After a quick read of the two links you gave, I had hoped that I might
have the answer since they both deal with exactly the error I"m
getting, but apparently not.

The first suggests that the problem is that the connection string is
embedded in the XSD file, and when you use a different server, then it
can no longer find the DB and can't parse the file. But in examining
my XSD files, they are taking the connections string from the
web.config file, where it has been changed. So that one didn't help.

The second one traced the problem apparently to conflicting versions
of the MySql connector. But since I am including the MySQL connector
dll that I used for development in the web load (and I believe I have
verified that it is using the one I am including - when I delete mine,
it gets a "can't find assembly" error, and when I put it back it gets
to the parser error), this does not seem to be the problem either.

I do appreciate your help though.
On Apr 16, 3:00 pm, "George Ter-Saakov" wrote:
> Did you google it?
> Check out folowing links
>
> http://forums.asp.net/p/1011934/1829242.aspxhttp://www.veloc ityreviews.com/forums/t365122-dataset-using-mysql-ren...
>
> George
>
> "daveh551" wrote in message
>
> news:7a9a43bb-08d3-49d0-9a1b-e92375f05156@t54g2000hsg.google groups.com...
>
> > I've developed a site using Visual Studio 2005, ASP.NET, C#, and a
> > MySQL database. I've gotten it debugged under the visual studio
> > environment, and moved it over to the server on my Domain Controller
> > (Window 2000 Server, IIS 5.0) and checked it out outside the
> > development environment.
>
> > So I went ahead and got a hosting account (GoDaddy Economy), imported
> > my MySQL database and checked it out, copied my site using the "Copy
> > Web Tool" in VS, changed the connection strings in the web.config
> > file, and tried to fire it up.
>
> > The first thing I got was that it couldn't load the MySql connector
> > assembly that was called for ( > > Version="5.2.1.0",...>. When I called their tech support the tried to
> > convince me there was something wrong with my connection string, and
> > when I insisted that wasn't my problem, the fell back to "We provide
> > the hosting space. The rest is up to you!" (Oh, well, I guess you get
> > what you pay for!).
>
> > I solved the problem (I think) by including the MySql.Data.dll in the
> > bin directory. But now it's blowing up with a "Parser Error" on line 1
> > of the .xsd file for the dataset I'm using. At least line 1 is what's
> > high-lighted in red on the error page. Line 1 is nothing more than the
> > XML version definition:"" (The
> > error was "Failed to generate code. Exception of type
> > 'System.Data.Design.InternalException' was thrown.")
>
> > What the heck? I have no idea how to even begin to figure out what has
> > gone wrong between my environment and theirs that can cause this. Both
> > my environment and theirs are running .NET Framework 2.0.50727.
>
> > Can anyone provide any help? Thanks.