Issues with download / installation of Atlas December bits

Apparently there are some issues with getting the correct Microsoft.Web.Atlas.dll and other annoyances when downloading the December bits. Jonathan Hawkings has a good summary of what to do on the ASP.NET forums, and I reproduce it here:

It looks like there is a replication issue with the ASP.NET ‘Atlas’ December ’05 release family on MS Download Center (download.microsoft.com). The December bits were originally released with the October release family (a download center deployment term) and they suspect this lead to the October bits continuing to be downloaded. The download center folks have since re-release the ‘Atlas’ December bits with a new release family.

Please try the steps below to clear our prior ‘Atlas’ versions from the IE cache, VS project templates etc.


1. Make sure you are running ASP.NET 2.0 RTM, Visual Studio 2005 RTM or Visual Web Developer RTM … ASP.NET ‘Atlas’ will only run on the RTM releases. Beta2 will not work. If you don’t have a 2005 RTM release you can download the RTM release of Visual Web Developer from http://msdn.microsoft.com/vstudio/express/vwd/download/. Uninstall prior beta 2005 releases.


Verify your version numbers by choose Help -> About in Visual Studio 2005 / VWD

Microsoft Visual Studio 20005 8.0.50727.42

Microsoft .NET Framework 2.0.50727


Close Visual Studio / Visual Web Developer


2. Clear out your Internet Explorer cache

Internet Explorer -> Tools -> Internet Options -> Delete Files

Close Internet Explorer


3. Delete older releases of the ASP.NET ‘Atlas’ VSIs


Zip files

C:\Documents and Settings\username\My Documents\Visual Studio 2005\Templates\ProjectTemplates\Visual Web Developer\CSharp\ASPNETAtlasWebApplicationCS.zip
C:\Documents and Settings\username\My Documents\Visual Studio 2005\Templates\ProjectTemplates\Visual Web Developer\VisualBasic\ASPNETAtlasWebApplicationVB.zip


Directories

C:\Documents and Settings\username\Application Data\Microsoft\VisualStudio\8.0\ProjectTemplatesCache\Visual Web Developer\CSharp\ASPNETAtlasWebApplicationCS.zip
C:\Documents and Settings\username\Application Data\Microsoft\VisualStudio\8.0\ProjectTemplatesCache\Visual Web Developer\VisualBasic\ASPNETAtlasWebApplicationVB.zip


4. Start Internet Explorer and download the December VSI

a. Navigate to http://atlas.asp.net/ (which redirects to http://www.asp.net/default.aspx?tabindex=7&tabid=47)

b. Click the link “Atlas Blank Project VSI (December release)”

c. Click the link “VSI file for creating a blank ASP.NET "Atlas" Web site”

d. Click the link “I Accept” (the link should point to cfab4430-426d-4a04-954b-1acbf852e800/ASPNETAtlas.vsi )

e. Choose “Open”, Next, Finish, Close to install the December VSI



5. Start Visual Studio 2005 / Visual Web Developer 2005 and create a new ‘Atlas’ Web site

a. File -> New Web Site -> ASP.NET ‘Atlas’ Web Site

b. The Readme.txt should contain “Date: 12/19/2005” which is December 19, 2005.



6. Read the ASP.NET ‘Atlas’ Technology Preview December 2005 release summary change list at:

a. Navigate to http://weblogs.asp.net/atlas/archive/2005/12/22/433869.aspx

Comments

Post a Comment

Popular posts from this blog

Some observations on Script Callbacks, "AJAX", "ATLAS" "AHAB" and where it's all going.

I've taken a more than cursory interest in the whole Remote Scripting (.NET species) vs. AJAX and now ATLAS discussion, mostly because I started using Remote Scripting since Microsoft first released it, and because I continued to refine it after seeing Brent Ashley's excellent work with JSRS, which was one of the first "real" cross-browser solutions back in 2000 (that's the turn of the Century for you history buffs). Now Bertrand Leroy, a Microsoft guy whose work I like , has authored some very interesting ASP.NET 2.0 script callback stuff that he points to on his blog, and he is obviously (at least, to me he is) involved quite heavily in the development of this new ATLAS infrastructure that they'll preview at PDC. Leroy's most recent post brings to the surface what I agree are the major differences between the "AJAX a - la .NET" approach as popularized by Michael Swartz with his AJAX.NET library, and Leroy's RefreshPanel, the ASP.NET 2.0 b
Read more

IE7 - Vista: "Internet Explorer has stopped Working"

Image
This one was a bitch. All of a sudden for no reason at all, out of the blue, I get this dialog "internet Explorer has stopped working". I didn't install any new software, crap- I didn't do anything! So here I am using FIREFART to go on the internet and find out what to do! Damn! Good thing I've got the sucker on the same machine (I'm not "anti-Firefox", i just don't use it that much except to check my page renderings). The Fix The fix (at least for me): 1) Go into Control Panel, and choose "Internet Options". 2) Under the "Advanced" tab, press the "RESET" button at the lower right: Don't ask me why this happens, or why the fix works. That's a BUG, D00D - I don't care how you slice it!
Read more

FIREFOX / IE Word-Wrap, Word-Break, TABLES FIX

One of the most annoying things a developer (who would normally delight in writing code, not futzing with markup) can have is getting rendering issues between different browsers. The two biggest players are of course Internet Exploder and Firefart (as I lovingly like to refer to each). In most cases that's going to take care of 98 percent of your total site traffic. IE has had a proprietary "word-break" style attribute for a long time, and this made it into the CSS 3.0 spec. But that doesn't necessarily help you with Firefox right now. Firefox literally - (and I consider this completely idiotic, since it's been in their bug database for FIVE YEARS) does not have a reliable CSS style element to force table cell content to break in the middle of a word in order to stop the content from expanding your table / div off the page or over other content on the page. Here's a partial fix, which will work for most tables and browsers. The style declaration (I call it m
Read more