My development team has been working on a company module and we encountered problems with certain code segments, but only on our pre-rollout server. The server is running Windows 2003, and DNN 4.0.1. Our dev team is running the exact same source (copied
directly from our dev machines from Source Safe), same database, but run it locally on our dev machines which are running XP Professional. The only thing different is the hosted environment.
These things are causing errors on the 2003 server:
Override Methods
Multiple classes in a single file.
Any thoughts as far as settings or permissions that could be causing issues? Network Service has Full access to the entire directory, just wondering if the IT department pushed some sort of policy that would be in the way. They won't be of much help in telling
us what they push unless we know what they pushed. I'm sure many of you know what I'm talking about who work in this type of environment.
We found that when working with .NET 2.0, and code is updated to an IIS directory, whether it is by a file transfer or change in Visual Studio, the precompiled DLLs don't always get updated. So IIS or .NET doesn't recognize the link between the precompiled
DLLs and the application which causes an error. Usually that it can't find a DLL or an object.
You have to delete the precompiled application from the temp folders in c:\Windows\Mocrosoft.Net\Framework\v2.0.50727\Temporary ASP.NET Files\
This forces the machine to recompile and will provide your machine with updated code.
I have just started converting some modules over to .Net2 and am having some strange errors as well.
I develop on a winxp box using iis5. The server is win2003 iis6. The module runs perfectly on the winxp iis but after I precompile, create a PA, upload it in DNN on the win2003 server, the module fails. I usually see the 'MinMax persistance requires a moduleID'
error, but looking in the log viewer, I see two other errors before that one.
For example: In the aspx page, I have a datagrid that calls a function:
<%# GetValueText(DataBinder.Eval(Container, "DataItem.Value")) %>
In the Codefile I have defined :
Private Function GetValueText(ByVal Value
As Integer)
As String
The log viewer shows this error:
error BC30451: Name 'GetValueText' is not declared
I changed the function to a Public Function and the error did not re-occur.
Another example:
In the aspx page, a tag '<dnn:sectionhead.....'
The error reported: 'Page' is not a member of .... class.
None of these errors occurs if I do not precompile the website and just copy the module directory completely over and add the App_Code directory. The module works as expected.
Are there different rules when developing modules with the intent of precompiling vs just deploying the entire source code with the module?
I am currently baffled with this. Any help would be great.
None
0 Points
26 Posts
Strange Code Behavior - DNN 4.0.1 - Single Machine
Jan 18, 2006 11:11 AM|jeremypettit|LINK
My development team has been working on a company module and we encountered problems with certain code segments, but only on our pre-rollout server. The server is running Windows 2003, and DNN 4.0.1. Our dev team is running the exact same source (copied directly from our dev machines from Source Safe), same database, but run it locally on our dev machines which are running XP Professional. The only thing different is the hosted environment.
These things are causing errors on the 2003 server:
Override Methods
Multiple classes in a single file.
Any thoughts as far as settings or permissions that could be causing issues? Network Service has Full access to the entire directory, just wondering if the IT department pushed some sort of policy that would be in the way. They won't be of much help in telling us what they push unless we know what they pushed. I'm sure many of you know what I'm talking about who work in this type of environment.
None
0 Points
26 Posts
Re: Strange Code Behavior - DNN 4.0.1 - Single Machine
Jan 30, 2006 04:10 PM|jeremypettit|LINK
We found that when working with .NET 2.0, and code is updated to an IIS directory, whether it is by a file transfer or change in Visual Studio, the precompiled DLLs don't always get updated. So IIS or .NET doesn't recognize the link between the precompiled DLLs and the application which causes an error. Usually that it can't find a DLL or an object.
You have to delete the precompiled application from the temp folders in c:\Windows\Mocrosoft.Net\Framework\v2.0.50727\Temporary ASP.NET Files\
This forces the machine to recompile and will provide your machine with updated code.
None
0 Points
90 Posts
Re: Strange Code Behavior - DNN 4.0.1 - Single Machine
Jan 30, 2006 09:29 PM|Boskone|LINK
I have just started converting some modules over to .Net2 and am having some strange errors as well.
I develop on a winxp box using iis5. The server is win2003 iis6. The module runs perfectly on the winxp iis but after I precompile, create a PA, upload it in DNN on the win2003 server, the module fails. I usually see the 'MinMax persistance requires a moduleID' error, but looking in the log viewer, I see two other errors before that one.
For example: In the aspx page, I have a datagrid that calls a function:
<%# GetValueText(DataBinder.Eval(Container, "DataItem.Value")) %>
In the Codefile I have defined :
Private Function GetValueText(ByVal Value As Integer) As String
The log viewer shows this error:
error BC30451: Name 'GetValueText' is not declared
I changed the function to a Public Function and the error did not re-occur.
Another example:
In the aspx page, a tag '<dnn:sectionhead.....'
The error reported: 'Page' is not a member of .... class.
None of these errors occurs if I do not precompile the website and just copy the module directory completely over and add the App_Code directory. The module works as expected.
Are there different rules when developing modules with the intent of precompiling vs just deploying the entire source code with the module?
I am currently baffled with this. Any help would be great.