User1843806588 posted
Thanks for all the responses.
How did you publish to IIS?
Right now, I'm publishing to a local directory, zip that up and then unzip it into the site directory on the server file system. In the past, we've published directly to the server file system via network share but that proved to be WAY too unreliable.
So Visual Studio compiles it and then copies the files over to the production directory.
Have you checked whether there are related messages in the Event Viewer?
The Event Viewer just references the same errors I mentioned in my first post.
Any reason for moving from code behind to inline...
Because I am tasked with moving as much code to inline as possible. This is because we have to wait an entire day and bring the production site down after-hours to make minor changes, and then hope it doesn't take all night - or all weekend while I'm
not being paid - to troubleshoot why the site didn't publish properly. The deficit in performance is considered a reasonable compromise for speed of development.
This will limit publishing to changes in classes and modules, and page logic can be altered immediately.
Where is defined the class you created?
All classes and modules are created in the App_Code directory. These are then compiled and not copied to the server.
You can use the @ Import directive to use the needed namespace or for a start, just try to type the full namespace in your code.
I tried this and also tried adding my class and module to a namespace. Just as before - this worked locally in Visual Studio, but not when published to the server.
If you try to mix code behind and inline scripting, you may also have issues because of the compilation model (ie the code generated from the aspx page inherits from the code behind compiled
code) and/or your deployment mode ie precompilation vs full compilation.
Both of these issues are red flags to me. These are topics I'm also not too familiar with, and I'm not sure how to deal with them. I was able to change the publishing option "Precompile during publishing" check box, but that didn't make a difference.
To be clear, all I am doing is taking an existing page that functions properly and moving a couple of existing code-behind events to Inline. Since it works seamlessly in Visual Studio, I'm convinced it's just a matter of making the application
configuration happy on the server - possibly a compilation issue. I'll explain the current code layout and the changes I made below.
I guessing you forgot to update the page directive. the page directive is still pointing to a partial class or file.
I removed the reference to the code-behind file and removed the code behind file completely - and it didn't like that.
Ok, the money-shot:
Public Class Login
Inherits System.Web.UI.Page
Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load
' Login Page Load code goes here:
End Sub
Protected Sub btnLogin_Click(sender As Object, e As EventArgs) Handles btnLogin.Click
' Login code goes here:
Dim objEventLog As New My_EventLog() ' the Class in question
End sub
End Class
Above is the code-behind file - Login.aspx.vb - originally created by Visual Studio when I added the page. I then CUT the subs out of code-behind and put them on the .aspx page which CURRENTLY looks like this:
<%@ Page Title="" Language="vb" AutoEventWireup="false" MasterPageFile="~/Site.Master" Inherits="MYPROJECT.Login" %>
<asp:Content ID="Content1" ContentPlaceHolderID="MainContent" runat="server">
<script Language="vb" runat="server">
Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load
' Login Page Load code goes here:
End Sub
Protected Sub btnLogin_Click(sender As Object, e As EventArgs) Handles btnLogin.Click
' Login code goes here:
Dim objEventLog As New My_EventLog() ' the Class in question
End sub
</script>
<!-- HTML goes here: -->
</asp:Content>
