locked
Published but .aspx.vb files not deployed RRS feed

  • Question

  • User507956310 posted

    Hi Guys,

    I published my brand new site the first time to the brand new server and when testing it I noticed that none of the .aspx.vb code behinds was deployed and I got an error that those were missing. Why did that happen? 

    Thursday, June 10, 2010 9:30 AM

Answers

  • User-925286913 posted

    How do you actually do Publishing?

    Are you using Publish option from Build menu or Right-Click menu from Website?

    Have you followed: http://msdn.microsoft.com/en-us/library/20yh9f1b%28VS.80%29.aspx


    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Friday, June 11, 2010 5:31 AM
  • User507956310 posted

    Hi,

    well its not that difficult to press the build - > publish button and enter the server details. I guess its just some bug

    under some circumstances.

    its all fine when I upload the aspx.vb files as well. time to get the vwd 2010 express and stop using the beta 2010.

    thanks for the suggestions.


    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Saturday, June 12, 2010 11:24 AM

All replies

  • User1027907351 posted

    The codebehind files are compiled into dll and located in bin folder. What is the error message?

    Thursday, June 10, 2010 9:38 AM
  • User-925286913 posted

    Code files (.vb or .cs) files are compiled in DLL (assembly). You don't have it after deployment.

    Refer:

    http://forums.asp.net/t/1380544.aspx

    http://stackoverflow.com/questions/357769/how-can-i-use-the-publish-function-in-visual-studio-2008-without-erasing-the-co

    http://weblogs.asp.net/scottgu/archive/2008/01/28/vs-2008-web-deployment-project-support-released.aspx

    Thursday, June 10, 2010 9:39 AM
  • User507956310 posted

    H Guys ,

    the error is

    parsererror:  /Members/LayoutMask02.master.vb can not be found


     <%@ Master Language="VB" CodeFile="LayoutMask02.master.vb" Inherits="members_Layout02" %>

    Thursday, June 10, 2010 4:17 PM
  • User1027907351 posted

    Is the error occured during build and publish or is a runtime error?

    Check whether you got the error when you executed in local machine without published.

    Check whether LayoutMask02.master and LayoutMask02.master.vb are both in Members folder when build and publish.

    Make sure virtual directory is pointing to the published folder.

    Thursday, June 10, 2010 11:17 PM
  • User507956310 posted

    Hi Peter,

    THe publishing works without errors. locally its obviously all fine.
    then after publishing I visit my website www.xxxxxx and there it comes,
    the error.
    pages without a master page work fine.


    looking via ftp at the directoy, indeed, the master.vb files are missing,
    they have not been "copied over". so when I move them there myself via
    ftp it all works.

     

    Friday, June 11, 2010 5:12 AM
  • User-925286913 posted

    How do you actually do Publishing?

    Are you using Publish option from Build menu or Right-Click menu from Website?

    Have you followed: http://msdn.microsoft.com/en-us/library/20yh9f1b%28VS.80%29.aspx


    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Friday, June 11, 2010 5:31 AM
  • User507956310 posted

    Hi,

    well its not that difficult to press the build - > publish button and enter the server details. I guess its just some bug

    under some circumstances.

    its all fine when I upload the aspx.vb files as well. time to get the vwd 2010 express and stop using the beta 2010.

    thanks for the suggestions.


    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Saturday, June 12, 2010 11:24 AM
  • User1081830283 posted

    I know this a very old thread and it was marked answered to boot, but in case this can help someone in the future.  I had the same issue were my code behind files were not getting deployed to my site when using MSDeploy.  In my case the solution was pretty simple (and provided by Benson Yu on this thread).  The problem was that the pages that exhibited the issue were using the 'CodeFile' attribute instead of the 'CodeBehind' attribute.  I believe this causes ASP.Net to look for the code file at run time instead of using the compiled assembly.  Changing the CodeFile attribute to CodeBehind solved the issue.

    Here's an example:

    original code:  <%@ Page Language="VB" AutoEventWireup="false" CodeFile="mypage.aspx.vb" Inherits="MyPage" ValidateRequest="false" %>

    changed to: <%@ Page Language="VB" AutoEventWireup="false" CodeBehind="mypage.aspx.vb" Inherits="MyPage" ValidateRequest="false" %>

    Wednesday, September 18, 2013 9:09 AM