Last post Sep 18, 2013 09:09 AM by asftissot
Jun 10, 2010 09:30 AM|polynaux|LINK
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?
Jun 10, 2010 09:38 AM|PeterCwpan|LINK
The codebehind files are compiled into dll and located in bin folder. What is the error message?
Jun 10, 2010 09:39 AM|chintanpshah|LINK
Code files (.vb or .cs) files are compiled in DLL (assembly). You don't have it after deployment.
Jun 10, 2010 04:17 PM|polynaux|LINK
H Guys ,
the error is
parsererror: /Members/LayoutMask02.master.vb can not be found
<%@ Master Language="VB" CodeFile="LayoutMask02.master.vb" Inherits="members_Layout02" %>
Jun 10, 2010 11:17 PM|PeterCwpan|LINK
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.
Jun 11, 2010 05:12 AM|polynaux|LINK
THe publishing works without errors. locally its obviously all fine.
then after publishing I visit my website www.xxxxxx and there it comes,
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.
Jun 11, 2010 05:31 AM|chintanpshah|LINK
How do you actually do Publishing?
Are you using Publish option from Build menu or Right-Click menu from Website?
Have you followed:
Jun 12, 2010 11:24 AM|polynaux|LINK
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.
Sep 18, 2013 09:09 AM|asftissot|LINK
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" %>