Publishing AtlasControlToolkit "The server block is not well formed"

I just downloaded this toolkit and it worked great. I wanted to publish it on our dev server so I could easily show my co-workers the site.

I got the following error when I tried accessing it,

Parser Error

Description:An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message:The server block is not well formed.

Source Error:

Line 1: <%@dotnet.itags.org. page language="C#" masterpagefile="~/DefaultMaster.master" autoeventwireup="true" inherits="_Default, App_Web_jupskp7v" title="Microsoft "Atlas" Control Toolkit" %>Line 2: Line 3:

Source File:/AtlasControlToolkit/Default.aspx Line:1

---

Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42

I edited default.aspx from this,

<%@dotnet.itags.org. Page Language="C#" MasterPageFile="~/DefaultMaster.master" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="_Default" Title='Microsoft "Atlas" Control Toolkit' %>

to this,

<%@dotnet.itags.org. Page Language="C#" MasterPageFile="~/DefaultMaster.master" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="_Default" Title='Microsoft Atlas Control Toolkit' %>

I removed the " surrounding Atlas in the title. The site worked fine after this.

Perhaps this should be changed in the toolkit so others do not have the same difficulty.

As I see it, the released sources (/Default.aspx) look like this:

Title='Microsoft "Atlas" Control Toolkit'

Therefore, I suspect that most people will not run into this problem.

Thanks!

That is what mine looked like too.

I published the web site to a dev server here and it resulted in this:

title="Microsoft "Atlas" Control Toolkit"

It worked fine on my local box, just not after I published it. Perhaps it is an issue with the publish feature.

Yes, this appears to be an issue with the publish feature. I tried to work around it by switching to:

Title="Microsoft "Atlas" Control Toolkit"

But publishing again munged it into the same string you had troubles with.

I don't think this is a big deal since the sample site is just for demonstration purposes, but if someone knows a good way to avoid the problem, I'd love to hear it.

Thanks for noting this!

I just switched the quotes around and it solved the problem for me...

Title="Microsoft 'Atlas' Control Toolkit"

Publishing site with new AJAX Beta 1

My previous Atlas-enabled sites using the juli ctp version behaved just fine, but when i upgraded there are errors.

Since the new version, you get to install the Ajax-extension libraries and there is no need to include the dll-file in the bin-directory of the app.

But how do I solve this when uploading it to my webhotell?

Do i have to copy the'Microsoft.Web.Extensions.dll' from the installationdir into the bin directory of my app as before, and reference to it in the Page-directive, like I still do with theAjaxControlKit.dll library?

Thanks in regards / Joel

Thats what I did since my hoster is not ready to install the beta on their servers. There are several threads about this. Do a search on "GAC". If I recall you will have to set your application to "Full Trust" for it to function properly. This is the default setting on IIS but some hosters set it to Medium for security purposes. I created a dev area and published my app there with the beta to test it. I may have gotten lucky with my host leaving the setting on Full Trust. I don't do much with the client side code, mostly server side controls.

Thanks for answering. I tried this and ended up with a runtime error on the remote site, but i figure its just some fuzz with the web.config to solve.

But I wasnt aware that Full trust level was needed now? (Haven't encountered any AccessException yet) Im currently looking around for asp.net hosting with full trust since I need SocketPermission for some of my apps anyway, but can't seem to find any in Sweden. Servergrid looks most likely for the moment, with Full trust and sqlsrv 2005.

/ Joel

I am using bottomlinecom.net. Full trust wasn't even one of the questions I asked when I signed up but it looks like they are configured that way. Sometimes its better to be lucky then good.