Just ran into another interesting gotcha with ASP.NET 2.0, if you are using any form of DotNetNuke don't install it in the root of your website! When I test posted my current project to my own hosting server to work with, I got some very strange behaviour. After a fair amount of digging I stumbled on a post having to do with DNN and other apps having difficulties existing together if DNN was at the root level.

Reinstalled DNN as a vDir and put a redirect page up and everything came back to life!

Cheers,

Bob Porter

I have recently had occassion to enable an existing web site project for Atlas functionality. It was reasonably straightforward and I wanted to share some of the links I found that helped me along, as well as some of the unique issues I encountered.

Jay Kimble posted an article on CodeBetter.Com that was very helpful.

Scott Guthrie’s whole blog is a fantastic resource for all things Atlas and ASP. (For the longest time I thought his last name was Gu!) In particular take a look at his ASP.NET 2.0 Tips, Tricks, Recipes and Gotchas article.

And of course the home page for the Atlas project here is a great resource.

Now onto the unique issues I encountered, mostly what was happening was that I was getting no where when inserting an Atlas tag into my pages, the infamous “red squiggly line” kept showing up. After a great deal of wailing, gnashing and web searching I realized that I had installed the last 3 CTP releases on top of each other. So I cleaned everything off (literally, I ended up re-paving my laptop!!!) and reinstalled everything from scratch and only the latest and greatest which at the time of this writing is the July CTP release.

Once that was done, and yes I had other issues than just the Atlas stuff, I was gratified to not see red squiggles everywhere in my code!

I hope this helps point someone in the right direction if they end up where I was. Hopefully not quite as drastic a fix as mine however!

Cheers,

Robert Porter

Hmmm