Jim Zimmerman - ASP.NET, MVC, Ajax and ORM

Well you know you have reached true geek status when you start listening to .NET developer radio or what we are now calling podcasts. Podcasts are so cool. I love listening to shows I actually can learn from. I listen to DotNetRocks and aspnet podcast. I found that one recently. I am sure there are others, but I only know of those 2 right now. Here are the links to those podcasts:

http://www.dotnetrocks.com/

and

http://aspnetpodcast.com/CS11/blogs/

Enjoy!

Here are some of the links to the several libraries I discussed at the meeting tonight about the different AJAX style libraries for ASP.NET 2.0 and ASP.NET 1.1:


http://jason.diamond.name/weblog/2005/10/29/my-ajax-dot-net-release-12
http://anthem-dot-net.sourceforge.net/
http://atlas.asp.net

It was fun to hang out tonight and always love the pubs. Check out CarCentral.com and build your car, get a free price quote or find a used car. See you again, hopefully in fort lauderdale in February!

I was scratching my head trying to figure out how to automagically sort and page through a dataset in asp.net 2.0 without having to write my own custom code like I used to have to in .net 1.1. In my code behind I was calling my business object and then setting the datasource properties in the Gridview. I could not get the sorting and paging to work. It was driving me crazy. Then I read that you need to set the DataSourceID property of the GridView to a sqldatasource or objectdatasource.

So I created an objectdatasource and pointed it to my business ojbect function that was doing the search and returning a dataset. I set the parameters of the ObjectDataSource to use QueryString and then everything worked fine.

I then was able to delete all of the code in my code behind. Amazing. You can actually implement a fully functional GridView without writing any code in a code-behind page. I love it.

Ok, now I am writing this after panicking for about an hour after updating my server from .NET 2.0 beta 2 to .NET 2.0 RTM. After uninstalling beta 2 and then installing the rtm for .net 2.0 I noticed that my .net 1.1 sites no longer worked. Two things happened. On one of the 1.1 sites it changed all of the page mappings to 2.0. That was an easy fix, I just changed the mappings back to 1.1.

The second problem was stranger. I could not find any aspx pages on the site. Although I had proper mappings reset. The problem again was in the web service extensions. Believe it or not I went on that track after searching for "404 error only on aspx pages asp.net 2.0" and finding an old post of my own. Go figure. Anyway I went to IIS and clicked on Web Service Extensions. I noticed that the ASP.NET v1.1.4322 extension was not even there anymore and that it had gotten deleted. All you need to do is click the "Add a new web serice extension" link and then name it "ASP.NET v1.1.4322" and then browse to "C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll" when it asks after you type in the name. Do not forget to click the "Set extension status to Allowed". Everything should work fine now.

The other day I was trying to set up my bug tracking software on a server that was running only websites using the new asp.net 2.0 stuff. Well when I went to run the .net 1.1 application, I got a "Service Unavailable" errror in red. What the hell is this I thought. Well after many nights of just saying, well I don't need that app right now on this dev server anyway, I decided to dig into what was going on. I noticed that there was only one app pool running for IIS when I looked at the task manager. Then I thought that the two might be in conflict trying to access simlar resources. So I created a separate app pool for 1.1 and one for 2.0 sites. And magically it worked.

I hope this helps someone that is at their wits end trying to figure this one out. I feel your pain.

I am setting up a new windows 2003 server and I was pulling my hair out trying to figure out how to get my aspx page to show up in the browser. I kept getting a page not found 404 error for every aspx page but not .html pages.

So, I opened up IIS manager and went to Webservice Extensions and noticed that ASP.NET was prohibited. So I right clicked on it and set it to be allowed. In Windows 2003, all the webservice extensions are prohibited by default to ensure security.

Hopefully this will save someone some time when configuring a new windows 2003 box.

Some cool stuff microsoft is doing with AJAX - style applications. This site is very new and not yet complete, but you will get an idea of what they are doing. Pretty cool stuff.

http://start.com/developer/default.htm

Here is a link to a look at the Atlas technology.

http://beta.asp.net/default.aspx?tabindex=7&tabid=47

I am looking at it myself and hope to incorporate this into my presentation on Saturday, Sept. 24th, 2005 in Tallahassee for Code Camp.