Yes, we are dogfooding DNN 4.3.1 and experiencing a few issues:

1) The Forums RSS feed is under investigation to find the source of the problem

2) As much as we profiled the code base for performance prior to release, there is nothing like dogfooding to reveal performance issues based on actual usage patterns. We have already discovered a number of areas for improvement which are checked into the repository for testing. These problems are not related to ASP.NET 2.0 - but rather to the Membership, Profile enhancements in this version

3) ?? Example ??

4) This is a behavioral change in ASP.NET 2.0 ( not related to DNN )

5) This was a bug introduced in DNN 4.3 related to the injection of javascript. It has been resolved and is checked into the repository.

We will be doing a state of the union in a few days to determine if another point release is warranted ( based on the items discovered in dogfooding ).

9) The tabid of the "general dotnetnuke forums" link is 510 whilst it should be 795. It's anoying as I used that link alot to get back to the complete forum view

Regarding 8, how do you disable the client script in 4.x.x? I mean all of it. Too much attack surface. Do I just delete the necessary files?

4) "Remember Me" not working.

This function not working seems to be affecting users of various applications based on ASP.NET 2.0.  It seems that it is NOT a DNN specific issue (users of CommunityServer.org are reporting same problem when using the ASP.NET 2.0 edition of that application).  It seems that basically a "feature" that existed in ASP.NET 1.1 is now fixed in ASP.NET 2.0 so that it actually works, where it was ignored in ASP.NEt 1.1 (DNN 3.x).

I can't verify this myself, but I'd like to see the DNN team investigate and change the DotNetNuke.com web.config settings (now that it is running on ASP.NET 2.0) to see if its fixed. I am experiencing the problem. I have to log into DNN site every day.

In web.config,

<authentication mode="Forms">
    <forms name=".DOTNETNUKE" protection="All" timeout="60" />
</authentication>

The "timeout" value is now honored in ASP.NET 2.0, where it was ignored in ASP.NET 1.1. Time is in minutes, so cookie only last 60 mins. If it was changed to say a week (10080) or something...

Cathal blogged on this topic 11/8/2005 here: http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/233/Default.aspx

Jeff