Atlas VSIs will only work with VS 2005 Beta 2

I want to answer what will very likely be a FAQ for the Atlas VSIs. The current Atlas VSIs onhttp://atlas.asp.net will not work with PDC bits or with any RTM builds of VS 2005 such as the August CTP – you need to be on a Beta 2 build. There were breaking changes occurring between Beta 2 and the RTM build which would have made it more difficult to develop/test Atlas and get it all finished by PDC. By staying on Beta 2, our developers could focus on Atlas features.

The team is following up soon with a PDC build and we'll have it out on the site when it's ready.

-Rich

OK I seem to be a bit cognitively challenged this morning: as far as I can tell the files currently served up at that location are just zip files (vsi.zip) - they don't initiate the installation of anything at all, contrary to the installation instructions.
I'm really keen to get going on this, so how exactly do we get the files integrated with VS 2005 Beta 2 given that there doesn't seem to be an actual installation process? I'd manually put the extracted files where they need to be, but I don't have a clue right now.
Regarding my earlier whine about the installation not working: it turns out all I had to do was remove the ".zip" extension that IE wanted to add for reasons known only to itself.
I use Visual Studio 2005 July CTP, after delete the compiled error in web.config (appliesTo="Web"), then it runs fine.
There are several breaking changes between Beta 2 and RC0 so while you may be able to get the VSI and your app to build there's also a chance that the Atlas code will break in some place due to one of those changes. We built and tested on Beta 2 so we know it works (preview quality, at least).
The team should have a RTM build version out pretty soon, however.
-Rich
Yes, we are working on getting the RTM versions of the VSI's complete ASAP. Apart from the appliesTo change in web.config, there are some changes within the Microsoft.Web.Atlas.dll that 'may' cuase you breaks depending upon your application. The script files themselves are currently consistent between builds.

Atlas under IIS 7

I'm using vista beta 2 build 5456 and trying to get an atlas application running. I realize this is a beta OS, but I thought I would post here to see if anyone had any insight or maybe the devs can fix it if it's their problem. As soon as I run the page I get the error:

Culture 'tk-TM' is a neutral culture. It cannot be used in formatting and parsing and therefore cannot be set as the thread's current culture.

This may not be enough to go on, but if it isn't I'm sure I could look into it more for whoever may want to know more.

hello.

how do you get this error? i've just installed vista and i'm really curious to see how one can get this kind of error...

I just create a new atlas website and make it a web application under iis 7 and then i hit the default.aspx for that application on localhost and I receive this error.

hello.

i've just followed those steps and don't get any error. the only error i got was solved by using a new app pool and setting it so that it used the classical asp.net isapi dll...

I tried a new app pool and now I get this error:

Configuration Error

Description:Anerror occurred during the processing of a configuration file requiredto service this request. Please review the specific error details belowand modify your configuration file appropriately.

Parser Error Message:Couldnot load type 'System.ServiceModel.Activation.HttpModule' from assembly'System.ServiceModel, Version=3.0.0.0, Culture=neutral,PublicKeyToken=b77a5c561934e089'.(C:\Windows\Microsoft.NET\Framework\v2.0.50727\Config\web.config line217)
Ok I fixed the culture error. I had to go into the IIS 7.0 .NET globalization properties and set the culture and or ui culture to the correct one for your locale. Now my atlas apps are flying under vista with IIS 7.0.

Atlas to Ajax Migration issues

We began proting our application yesterday. Many things are different. In the long run, I think these are better bits. It the short run, the beta 1 seems alot less stable than the last release.

For example, We are getting this error message sproradically. Sys.WebForms.PageRequestManager

We also have some Custom Compiled Controls that used to work very well in the update panels, however, now they do not partial render, and sometimes, they redirect to no where, when watching through fiddler.

Are there any tricks in the new beta 1 for using Custome Compiled Controls with in an UPdate Pannel?

We have the simple code:

<asp:ScriptManagerID="ScriptManager1"runat="server"EnablePartialRendering="true"/>

<asp:UpdatePanelID="updPnlAddress"runat="server"RenderMode="Block"UpdateMode="Conditional">

<ContentTemplate>

<cc1:StoreFrontAddressControlID="StoreFrontAddressControl1"runat="server"/>

</ContentTemplate>

</asp:UpdatePanel>

Nothing is on the code begind. The control has a LinkButton on it, which changes the Labels to TextBoxes for editing. When the link is clicked the page actually refreshes.

Here is the request from fiddler

__EVENTTARGET=ctl11&__EVENTARGUMENT=&__VIEWSTATE=%2FwEPDwUJLTM4Njk1MDQ0D2QWAgIDD2QWAgIDD2QWAmYPZBYCAgEPZBYUZg8PFgIeBFRleHQFC01hcmlhIE5vdmFrZGQCAQ8PFgIfAAUPUmUvTWF4IFN1YnVyYmFuZGQCAg8PFgIfAAUUMjMxMSBXLiBTY2hhdWJ1cmcgUmRkZAIDDw8WAh8AZWRkAgQPDxYCHwAFFVNjaGF1bWJ1cmcsIElMLCA2MDE5NGRkAgUPDxYCHwAFDVVuaXRlZCBTdGF0ZXNkZAIGDw8WAh8ABQ4oODQ3KSAyMzAtNzMxOWRkAgcPDxYCHwAFEG1hcnJlbWF4QGFPTC5DT01kZAIIDw8WBh4JRm9udF9Cb2xkZx8ABRVFZGl0IFNoaXBwaW5nIEFkZHJlc3MeBF8hU0ICgBBkZAIJDw8WAh4HVmlzaWJsZWhkFixmDw8WCh8BZx4JRm9yZUNvbG9yCo0BHwAFHFBsZWFzZSBjb3JyZWN0IG1hcmtlZCBpbiByZWQfAgKEEB8DaGRkAgEPDxYCHwAFBU5hbWU6ZGQCAg8PFgIfAAULTWFyaWEgTm92YWtkZAIDDw8WAh8ABQhDb21wYW55OmRkAgQPDxYCHwAFD1JlL01heCBTdWJ1cmJhbmRkAgUPDxYCHwAFBkxpbmUxOmRkAgYPDxYCHwAFFDIzMTEgVy4gU2NoYXVidXJnIFJkZGQCBw8PFgIfAAUGTGluZTI6ZGQCCA8PFgIfAGVkZAIJDw8WAh8ABQVDaXR5OmRkAgoPDxYCHwAFClNjaGF1bWJ1cmdkZAILDw8WAh8ABQZTdGF0ZTpkZAIMDxBkDxYOZgIBAgICAwIEAgUCBgIHAggCCQIKAgsCDAINFg4QBQJBSwUCMTFnEAUCQ0EFATFnEAUCQ08FAjI4ZxAFAkRDBQMxMThnEAUCSUwFATNnEAUCTEEFAjE3ZxAFAk1PBQE1ZxAFAk5EBQIxM2cQBQJORQUBNmcQBQJOSAUCMTZnEAUCTk0FATdnEAUCTlYFAjE0ZxAFAlRYBQIyNGcQBQJXVgUCMzNnFgECBGQCDQ8PFgIfAAUEWmlwOmRkAg4PDxYCHwAFBTYwMTk0ZGQCDw8PFgIfAAUGUGhvbmU6ZGQCEA8PFgIfAAUKODQ3MjMwNzMxOWRkAhEPDxYCHwAFBkVtYWlsOmRkAhIPDxYCHwAFEG1hcnJlbWF4QGFPTC5DT01kZAITDw8WAh8AZWRkAhQPDxYIHwFnHglCYWNrQ29sb3IKXx8ABQlDYW5jZWwgICAfAgKIEGRkAhUPDxYIHwFnHwUKTh8ABQcgICBTYXZlHwICiBBkZGSnmKQVmPvdoG6CR%2BlpIzNu1oycfA%3D%3D&__EVENTVALIDATION=%2FwEWAgLkx9L4AQKiwPWxAlOkw%2Bolr0%2Bkb8bS%2FkBjgOOKf3pS

The response is the full page, and not the partial secion.

All help is appreciated.

hello.

yes, there are a lot of new things here. i'm not sure on what's the error you're getting, but i'm assuming that it says something like: can't parse the msg? if that is the case, then you're probably using response.write somewhere? this is not a good thing to do in an ajax page. btw, if you search this forum, you'll find several posts about it (maybe one will help you).

regarding the updatepanel, there are some posts about it here:

http://forums.asp.net/thread/1440058.aspx

http://forums.asp.net/thread/1445844.aspx

Yes. I finally ran across these posts. A developer on another project turned trace on. With the nice inherrited configs, our app turned trace on. We are all set.

However, the custom control does not work. I need to figure this out. I will post the solution.

We have also run into some wierd inconsitancies with the page model. We have had to move some code behind logic out of PreRender and into load. So far its been, Dynamic populate and ratings control affected.

Geoff

hello.

sorry, but i'm not a toolkit control user yet so i think i won't be able to help you with those controls.

Atlas timeline

Hi

I'm building a application and are looking to add AJAX functionallity to it around may/june. But I'm not interested in using a alpha or beta version so it would be nice if any of the developers of Atlas could present a timeline for it. So I, and probably others too, can start planing for it in our own projects timeline.

And it would also be nice if you could tell a little of what kind of webcontrols/functionallity are planed to be in the final release.

Thanks.

Hi DiCoo,

We are going to be making some announcements regarding Atlas timing next week. Specifically, we are going to announce a go-live license that will be coming this spring -- which will allow you to deploy applications using the Atlas CTP drops.

Hope this helps,

Scott

If I understood it correctly, I cannot deploy my web site built with ATLAS dec CTP even thought it is only a personal site, e.g. non-profit hobby site ?

So I'll have to wait a couple of months (I am eagerly awaiting announcement next week) till I can upload it with atlas changes?

I didn't know that (tell me about reading the eulas :-), now I need to rewrite it haha...
Sounds great, thanks.

agarwaen wrote:

If I understood it correctly, I cannot deploy my web site built with ATLAS dec CTP even thought it is only a personal site, e.g. non-profit hobby site ?

So I'll have to wait a couple of months (I am eagerly awaiting announcement next week) till I can upload it with atlas changes?

I didn't know that (tell me about reading the eulas :-), now I need to rewrite it haha...

we can't? i thought based on terms of use:

Unless otherwise specified, the Services are for your personal and non-commercial use. You may not modify, copy, distribute, transmit, display, perform, reproduce, publish, license, create derivative works from, transfer, or sell any information, software, products or services obtained from the Services.

shldn't this say that we can?

The first paragraph of the license specifies:

"INSTALLATION AND USE RIGHTS.

You may install and use any number of copies of the softwareon your premises to design, develop and test your programs for use with the software running on the Microsoft .NET Framework 2.0 component of the applicable Microsoft Windows operating system.

You may not test or otherwise use the software in a live operating environment unless Microsoft permits you to do so under another agreement. You also may not use the software to deploy or publish web applications for any use by third parties. "
That does clarify it. However, there are many sites on the internet that give examples, and a live example on ways of working with atlas.

There are a few MS employees who have sites that feature atlas, as well as many bloggers who have atlas examples on their website. (live examples, with code).

Those examples provide no functionality to their site, only a means of helping the development community work with it. Are they breaking the license, or are those examples based on a "non-live operating environment"?

Yes, they are breaking the license unless they have a special aggreement with us.

Edit: they are breaking the license if the examples are *live*. Publishing code samples and articles is perfectly ok and even encouraged.

ScottGu wrote:

Hi DiCoo,

We are going to be making some announcements regarding Atlas timing next week. Specifically, we are going to announce a go-live license that will be coming this spring -- which will allow you to deploy applications using the Atlas CTP drops.

Hope this helps,

Scott

Has the go-live license announcement happened? If so, where can I find it?

Thanks

I am a little confused.Is a web site or a blog that has Atlas samples or tutorial, but it doesnot include the Atlas dlls and the javascripts to download, breaking the law? Can I publish tutorials, samples and documentation on my blog without the Atlas dlls? Do I need to remove any matter regarding Atlas that has been already published?

You are very much encouraged to talk about Atlas all you want, as well as write and publish sample code. The license does not prevent that in any way, fortunately.

ScottGu wrote:

Hi DiCoo,

We are going to be making some announcements regarding Atlas timing next week. Specifically, we are going to announce a go-live license that will be coming this spring -- which will allow you to deploy applications using the Atlas CTP drops.

Hope this helps,

Scott

Is there a go-live date yet?