Are the developers of ASP.NET Ajax stupid?

hello.

well, it seems like that is needed in order for some of the features to work (this already happened in the previous release).

I really hope that they have a way of making it work in Medium Trust.

The new beta 1 documentation states in the "Asynchronous Communication Layer Overview" (http://ajax.asp.net/docs/Overview/intro/async/default.aspx) that a feature of the layer is that "It can be used with Medium trust". (See the online docs if you're interested.) I haven't found the documentation that tells you how to configure it however.

ASP.NET AJAX Beta1 supports medium trust and partial trust environments.

Storing an assembly in the GAC does not in any way prevent the ability to run in medium/partial trust scenarios.

Hope this helps,

Scott

I am currently hosting my asp.net site in NetworkSolutions. They won't install any beta products. So how do I take advantage of Asp.Net Ajax beta v.1.? If I copy "Web.Extensions.dll" into bin folder then security blocks "ScriptManager execution. I am really stuck here. Any solutions? if yes what will be the web.config settings? I am now considering Dojo v.4. Anyone use this framework?

Thanks

Achu.

Ideally they would install the Beta Extensions. These won't modify ASP.NET 2.0 at all, and won't affect anyone on the box who doesn't configure their web.config file to use them.

If you want to just use the client-side features (and not use the server controls), you could alternatively just copy the .js files up with your application and directly reference them from your pages (using a regular <script src="http://pics.10026.com/?src="> reference). This would give you a similar experience to Dojo - although you wouldn't have any of the server features (note: Dojo is also client-only and doesn't have server features).

Hope this helps,

Scott

So it will not work from the bin folder and must be in the GAC? I noticed this in the release notes but did not see a reason given. Since I have FTP access only this is kind of a bummer.

Also between all the added goodness of WSE, AJAX Beta, CTP...etc deploying the dlls and web.config changes is becoming a bit of a nightmare.

Scott,I'm confused. That statement directly contradicts other statements in these forums and on various blog posts (including comments from members of the ASP.NET team). What's the story here?

I'm annoyed too. My ISP has a medium trust (shared hosting) configuration and my ScriptManager doesn't work anymore (as it did at Atlas time).

I'm keeping my eyes on this thread hoping for a quick solution.

(bad release anyway, it's not about the technology itself but surely about times, modes and reliability).

There are a couple of things to clear-up on this thread. First some background:

-- Assemblies can be installed either in the GAC (global assembly cache) or in a local \bin directory with ASP.NET. Microsoft assemblies that need to be servicable (meaning Microsoft can release patches for them) need to be installed in the GAC. Because ASP.NET AJAX will be a fully supported product from Microsoft, the plan is to install it into the GAC.

-- Assemblies can support partial trust when copied into the GAC. Adding an assembly into the GAC *does not* mean it requires full trust.

-- When ASP.NET AJAX Beta1 is copied into the GAC of a server, it can be used in partial/medium trust just fine by any application on it. So if your hoster has installed ASP.NET AJAX Beta1 on a remote system, you are set -- it will work fine in medium trust.

The problems in the above thread occur when your hoster hasn't installed ASP.NET AJAX Beta1 onto a system yet. Because of the way the Beta1 assembly is marked, it doesn't support simply copying into the \bin directory and having it work in partial trust. It has to be installed in the GAC of the system to support medium trust.

We are working hard with hosters to get them to install the ASP.NET AJAX Beta bits on their systems (meaning to add it to the GAC). Because this is a non-impactful install (it can't screw up anything on the machine), it is a very safe thing to-do and shouldn't cause any problems to any application. Once they install it, then you can simply copy your apps up to the remote system without any problems and have them run in partial trust.

Since we know that some developers will have hosters that are slower in updating systems, we are also investigating possibly releasing a special ASP.NET AJAX build in the next week or two that will support deployment in the \bin directory of an application. This will provide a temporary workaround in case your hoster hasn't installed ASP.NET AJAX on the system yet - and will support running in partial trust as well. Once your hoster installs ASP.NET AJAX, we'll recommend you remove the assembly from the \bin directory and just use the GAC installed one.

Hope this helps,

Scott

Thanks Scott,

that was perfectly clear. In fact I'm one of those whose hoster is ...slower! Let's say that it won't install anything that isn't final-release-marked.
I realize that it would be an "non-impactful" one but I surely cannot force my ISP policies, I also think that many providers around the world will act the same.
That is basically the reason I don't understand why the ASP.NET AJAX Beta hasn't been conceived as abin-deployable library.

Regards.

> That is basically the reason I don't understand why the ASP.NET AJAX Beta hasn't been conceived as abin-deployable library.

ScottGu:

Microsoft assemblies that need to be servicable (meaning Microsoft can release patches for them) need to be installed in the GAC.

Should be quite clear. ;)

Regards. -LV

Fine. Got it. But please help me with this further doubt (sorry but I'm not so in to the problem): why patching a Beta release? why not a Beta 2 release (always bin folder targeted)?
Please forgive me, hammering isn't my goal, it's just I'm finishing downgrading my app and it's 2.30 in the morning...

I enjoyed some of the new techincal aspects of this release, I really did! It's just about this deployment aspect...

Regards to MVPs, moderators and ASP.NET Team members, thanks for answering. Good night.

I am also downgrading from beta 1 to atlas... Beta 1 don't work... Please MS GUIs, release a beta 2 that works

thanks