In the default.aspx page I had to change...

Dim objCSSCache As Hashtable = CType(DataCache.GetCache("CSS"), Hashtable)

to

Dim objCSSCache As Hashtable = CType(DotNetNuke.Common.Utilities.DataCache.GetCache("CSS"), Hashtable)

 in order to make the error go away I did similar changes on several lines and now I am getting "Object Reference not set to an instance of an object" but with no page or line number to look at and debug. My dev box is windows XP Pro. The QA Server is Windows Server 2003 R2.

My question is it possible that some setting on the QA Server is causing this error? I don't think I should have to change any of the original DNN code as it was release quality. So I am thinking it has to be something about the environment. The app runs fine on all our machines except the QA Server.  Our dev team did not configure the QA Server, corporate IT did and it is appears to be on lockdown.

As always, thanks for any hints or advice,

Chris

What is happening is that if you do a compile of dnn on your QA server some of the DLLs get updated with new version codes.
These new dlls are then references by your modules instead of the DNN core versions.

When you then try to move any elements to production server - any compiled modules that u try to copy across will have references
to different versions of the core libraries.

Basically, you should not be compiling the DNN source code at all.
This will get you into all sorts of problems.

You should create a build environment for your development that turns off all compiles of the core since there is really no reason at all
for you to compile the core - and it also really slows down you development roundtrip times.

Westa